SoterHelp Center

Using Duck Creek with SoterAI

Connect Duck Creek to SoterAI and ask questions about your policy, billing and claims data without building reports.

Like every SoterAI connector, the Duck Creek connection is read-only: SoterAI can read and search your data, but it cannot create, edit, or delete anything in Duck Creek.

Assisted setup. Duck Creek is connected with help from our team. In the Connectors panel, its card shows Request setup instead of Connect. You bring the access details from your side, and we set up the connection to your workspace for you — there is nothing to install.

Every Duck Creek setup is configured differently, so we work from the API documentation for your own instance.

Before you request setup

Have the following ready before you send your request:

  • The Duck Creek product modules and version you run (for example Policy, Billing or Claims)
  • Your tenant API URL
  • Credentials
  • The API documentation for your instance

Your organisation will also need to allow SoterAI’s outbound traffic through your firewall. Ask our support team for Soter’s egress IP address in your setup request so you can add it to your allowlist.

Keep your credentials safe. Don't paste passwords, secrets or tokens into the request email. List which details you have ready, and our team will confirm how to share them securely. Use credentials scoped to the minimum access you need.

What SoterAI can access

Once connected, SoterAI has read-only access to:

  • Data from the Duck Creek modules in scope, such as policies, billing and claims records

Access is always limited to what the credentials you provide are allowed to read.

What SoterAI cannot do

  • Cannot create, edit, or delete records in Duck Creek
  • Cannot submit forms or trigger workflows inside Duck Creek
  • Cannot access data outside the scope of your credentials
  • Cannot change configuration, permissions, or user access

How to request setup

  1. 1Click the puzzle piece icon in the chat input bar to open the Connectors panel.
  2. 2Open the Available tab and find Duck Creek under Risk & safety (use the Search integrations bar if needed). The card shows a short summary of what we'll need.
  3. 3Click Request setup. A prefilled email to our support team opens, with the connector name and your workspace already filled in, plus the same checklist.
  4. 4Add any details you already have (without credentials) and send it.
  5. 5Our team will reply to arrange the next steps and set up the connection. Once it's live, Duck Creek appears in your Connected tab and you can use it in chat like any other connector.

If your email app doesn't open, write to help@soteranalytics.com with the subject ‘Connector setup request: Duck Creek’.

To remove access at any time, open the Connectors panel and click Disconnect on the Duck Creek card in the Connected tab.

Example queries

Once connected, just ask naturally.

Claims and losses

  • "How many open claims do we have by line of business?"
  • "Summarise loss trends for this account"

Policies

  • "Which policies have claims above a set threshold this year?"

Use cases

Claims and loss insight

Ask about open claims and loss trends in plain language, and get a summary by line of business or account without building a report.

Risk control planning

Use loss and claims patterns to decide where risk control effort will make the most difference.

Underwriting and renewal support

Review policy, billing and claims data together when preparing for an underwriting or renewal decision.

Troubleshooting

IssueSolution
My email app didn’t open when I clicked Request setupWrite to help@soteranalytics.com with the subject ‘Connector setup request: Duck Creek’.
SoterAI can’t see certain recordsAccess is limited by the permissions of the credentials you supplied. Ask your Duck Creek administrator to confirm what they can read.
Slow responses on large queriesNarrow your question, for example to a date range, site, or single record type.
Setup is taking longer than expectedDuck Creek setups vary between instances. Sharing complete, up-to-date API documentation for your instance speeds things up.

For more general help, see Troubleshooting external app connections.