If your claims team already uses Guidewire ClaimCenter, the Genesys Cloud integration can notify policyholders when a change in the claim triggers an update. Duck Creek Policyholder is another option for a carrier on Duck Creek. Before you choose, ask to see what happens after a policyholder uploads a missing photo. Can the software acknowledge that specific photo and cancel its reminder while a separate request for a receipt stays open? Guidewire and Genesys integration · Duck Creek Policyholder
Which call should the portal save?
A policyholder uploads the photo an adjuster asked for. The next morning, another message asks for the same photo. The policyholder calls to find out if it went missing. A claim-level label such as “under review” gives them little to go on. A dated acknowledgement beside the photo and an outstanding request beside the receipt answer two different questions. Did you get it? What do you still need from me?
For a Canadian example of what a customer can already do, Intact describes claim tracking and document uploads in its app and Client Centre. Its guide is a useful point of comparison when designing the customer view. The buying decision turns on how the portal and your claims system handle those documents together. Intact’s guide to online claims
Which software belongs on the shortlist?
- Guidewire ClaimCenter with Genesys Cloud. The vendors document proactive status notifications triggered by events in its systems. Ask the supplier to show the event that starts a notice in your line of business, the delivery channel and the rule that cancels a pending reminder. Genesys integration overview
- Duck Creek Policyholder. Duck Creek describes built-in notifications and a customer view of claim status. For teams using text messaging, the separate Hi Marley integration with Duck Creek Claims also documents scheduled messages and a record of conversations. Ask which components the quote covers and have the supplier demonstrate reminder cancellation in your configuration. Duck Creek Policyholder · Hi Marley integration sheet
For an independent adjuster or brokerage working in a carrier’s system, start with access. Can your team read the document request ID and the event confirming receipt? If staff still have to open the carrier’s portal to check, a staff-confirmed handoff may be the practical first step. A new messaging subscription cannot supply an event the carrier never shares with you.
Set up the demo and the quote
Ask for a fictional claim with two outstanding items, a policyholder login and an adjuster login. Use a test inbox and an environment where the supplier can bring a reminder due during the session. If brokers need access, use a separate broker account and verify which files it can see. Ask for separate figures for setup, integration, licences, message delivery, bilingual templates and ongoing support.
Follow a missing photo through its reminder deadline
This is an illustrative vendor demo script. For each step, record the time, the document request ID, what the policyholder sees and what appears in the adjuster’s file. Use the same starting conditions for each supplier.
- Request a photo and a receipt. Both appear as outstanding in the portal. The notice directs the policyholder to the secure claim. Details of the loss stay inside the authenticated view.
- Upload just the photo. Using the policyholder login, look for a time-stamped acknowledgement. The adjuster should find the same photo against the correct request. Receiving a file and accepting it as adequate evidence are separate decisions.
- Bring the reminder due. Check the test inbox and the send history. There should be no reminder for the received photo. The receipt should still be outstanding and remain eligible for its own reminder under the agreed rule.
- Repeat the upload event and simulate a delivery failure. A repeated event for the same upload should produce one acknowledgement. Try an unreachable test destination. An adjuster should see the failed delivery and know who will follow up. Record attempted delivery separately from confirmed delivery or a customer reading the notice.
- Ask for a clearer photo. If the first image is unreadable, have the adjuster open a new request with a reason. The customer should see what to resubmit. The file history should preserve the first upload and identify which request the new reminder belongs to.
What makes the demo a pass?
Watch the outstanding-item list when the reminder becomes due. If the photo returns to the list, or the receipt disappears with it, ask for a fix and a rerun. If the photo arrives after the reminder is queued, ask to see the final check against the current document state. Keep the pilot narrowly scoped to claims. A policy change or certificate request has a different owner and completion event.
Run the same case using French and English preferences. Check the notice, the acknowledgement and the wording shown when an upload fails. Provide an accessible route to an adjuster for a person who cannot use the portal or chooses another channel.
Before a pilot, have the appropriate owners review who can access the documents, where claim data and message logs are processed, and how long records are retained. To assess the effect on the contact centre, compare receipt-confirmation calls per 100 document requests over comparable periods and record changes in claim mix. This guide draws on supplier documentation. We did not run an insurer’s platform or send a message to a policyholder.
Shortlist checklist
- The policyholder can identify the outstanding item and see proof of receipt for the uploaded one.
- The photo reminder stops and the receipt keeps its own schedule.
- A failed notice or rejected document has a named follow-up owner.
- The proposal lists the required modules, costs and evidence from the demo.
For the wider claims workflow, see our guide to claims processing. If your claims system and portal disagree about which documents are outstanding, Hamdi Services can help define the integration. Custom applications and integrations

