RM Assistant for Dayd ALIS
Broker submissions become structured records in your Dayd ALIS instance — matched against existing policies, reviewed by a person, and traceable back to the source document.
Running against production submissions today.
What RM Assistant does with Dayd ALIS
Data flows into your system of record. We are the intake layer, not another place your data has to live.
Authenticated against your ALIS environment
The adapter authenticates directly with your ALIS (DX) instance and holds credentials encrypted per tenant. UAT and production environments are configured separately, so you can validate against UAT before anything touches live policy data.
Policy and quote lookup
Submissions are matched against existing policies and quotes in ALIS, so a renewal or a re-market is recognised as such rather than landing as a new unrelated record.
Structured submission data posted after review
Insured details, drivers, vehicles and loss history are written into ALIS once a person has approved them in the review queue. Nothing posts unreviewed.
Full traceability back to the source document
Every value posted keeps a pointer to the document and page it came from, so an ALIS record can always be reconciled against the original broker submission.
Dayd ALIS integration, answered
Is the Dayd ALIS integration live?
Yes. Dayd ALIS is the policy administration integration running in production today. It is the connector with the most operational mileage behind it.
How does RM Assistant authenticate with ALIS?
Through your ALIS instance's own token-based authentication. Credentials are stored encrypted and scoped to your tenant, and UAT and production are configured as separate environments so testing never touches live data.
Does data post to ALIS automatically?
Only after a human approves it. Extracted data lands in a review queue with field-level confidence and links to the source document; a person confirms or corrects, and then the record is pushed. This is deliberate — the goal is to remove the typing, not the underwriting judgement.
Can you validate against our UAT environment first?
Yes, and we recommend it. Standard onboarding runs your real historical submissions through the pipeline against UAT so you can measure accuracy on your own book before any production cutover.
What if our ALIS configuration differs from the standard one?
Field mapping is configured per tenant against your schema. Differences in how your instance is set up are handled in that mapping rather than requiring you to change your ALIS configuration.
Talk to us about Dayd ALIS
30 minutes, a real submission from your book, and a straight answer about where this integration stands for your instance.
Book a demoNo sales pressure. We confirm within one business day.