1. Before You Start
You will need:
CRM Administrator access on the customer instance.
A Dazos administrator account (only Dazos admins can enable iAssist per instance and generate API keys).
The RVK integration team on hand to receive the API key and endpoint details.
Access requirements: iAssist is switched on per customer instance by a Dazos administrator. Until it is enabled, the iAssist tab does not appear in AI Agent Settings and the endpoint rejects all requests.
⚠️ Note: If you don't see the iAssist tab in your CRM, contact Dazos support and ask for iAssist to be enabled for your instance.
2. Enable iAssist for an Instance
(Dazos administrators only)
Sign in to the Admin instance and open AI Agent Settings → Instance Mapping.
Find the customer instance in the list.
Tick the iAssist switch (alongside iConnect, iScreen, iRecover, and the other agents) and click Save.
The instance list shows an Enable iAssist column with an Active / In-Active badge so you can confirm the change. The Edit button on each row also lets you toggle iAssist later.
3. Open the iAssist Settings Tab
On the customer instance, navigate to CRM Integrations → AI Agent Settings. A new iAssist Agent tab appears next to the existing iConnect, iScreen, and iRecover tabs.
The tab contains, top to bottom:
Section | What it's for |
iAssist Agent Key | Generate and copy the unique API key for this endpoint |
iAssist Configuration | Pick the Record Creation Mode and the status/stage to set |
Field Mapping | One unified mapping screen (incoming fields → CRM fields), with saved mappings and default values below it |
Sub-table Mappers | Related Contacts, Medications, Treatment History, Substances of Abuse |
User Assignment | Round Robin or a specific user for new records |
Patient Matching | Duplicate handling for incoming patients |
AI Comments / Alerts / Availability | Notes-to-comments mapping, live-transfer and callback alerts, availability ping |
4. Generate the API Key
In the iAssist Agent Key card, click the Generate (refresh) button. (Dazos administrators only — other users can view and copy the existing key.)
Click the Copy button and share the key with the RVK integration team.
The key is unique to iAssist. It never overlaps with the iConnect or iScreen keys, so you can rotate it without touching the other agents.
5. Choose the Record Creation Mode
This single choice controls what iAssist creates from each submission. Select one option — it saves automatically and stays selected the next time you open the page.
Mode | Without a PAA in the submission | With a PAA in the submission |
Lead Only |
Creates/updates a Lead | Creates/updates the Lead and attaches the PAA under the Lead |
Always Convert | Creates an Account + Opportunity (+ VOB) | Same, with the PAA attached to the Opportunity |
Convert Only on PAA | Keeps the patient as a Lead | Converts to Account + Opportunity and attaches the PAA |
6. Set Lead Status and Opportunity Stage
Below the mode selector, dropdowns let you control what status or stage iAssist applies. They change with the selected mode:
Mode | Selectors shown |
Lead Only | Lead Status (no PAA), Lead Status (with PAA) |
Always Convert | Opportunity Stage (no PAA), Opportunity Stage (with PAA) |
Convert Only on PAA | All four of the above |
Every selector is optional — leave it blank and iAssist won't change that status or stage at all. The options come from your instance's own Lead Status and Sales Stage picklists.
Click Save iAssist Configuration after changing the selectors.
7. Map Fields
iAssist uses one unified Field Mapping screen per mode. The available destination fields automatically match the selected Record Creation Mode:
Mode | Destination fields shown |
Lead Only | Lead + PAA fields |
Always Convert | Account + Contact + Opportunity/Intake + VOB + PAA fields |
Convert Only on PAA | Lead + Account + Contact + Opportunity/Intake + VOB + PAA fields |
To add a mapping:
Pick the CRM Field (the destination) from the dropdown.
Pick the AI Agent Field (the incoming field name).
Click Save. The new row appears immediately in the Mapped Fields table below, where you can also delete mappings.
[📸 Screenshot Placeholder 3: Show the Field Mapping section with CRM Field and AI Agent Field dropdowns]
Additional controls on the same screen:
Control | Purpose |
+ Custom Field | Define a new incoming agent field name and map it in one step |
Default Field Values | Set fallback values used when the submission doesn't include a field (managed on the same screen, and also mode-aware) |
Sub-table mappers | Map the row-level fields for Related Contacts, Medications, Treatment History, and Substances of Abuse |
💡 Tip: Switching the Record Creation Mode instantly reloads the mapping screen — the field dropdown, saved mappings, and default values all refresh to the fields relevant to the new mode.
8. Patient Matching and Duplicate Handling
Turn on Enable Patient Matching to match incoming patients against existing records by mobile number, or by name + date of birth. The options shown depend on the mode:
Mode | Options shown |
Lead Only | Update Existing Lead |
Always Convert | Create New Intake Opportunity |
Convert Only on PAA | Both options |
How duplicates are handled:
If an incoming patient matches an existing Account, iAssist updates it and (when enabled) opens a new intake Opportunity on it — it never creates a duplicate Account.
If the patient matches an existing Lead, iAssist updates that Lead and, in a convert mode, converts that Lead — it never creates a second Lead for the same person.
Even with Patient Matching off, resending the same mobile number reuses the existing record instead of duplicating it.
9. User Assignment, Comments, and Alerts
These sections work like their iConnect/iScreen counterparts but are saved independently for iAssist:
Section | What it does |
User Assignment | Assign new records via Round Robin across selected users, or always to one specific user |
AI Comments Mapping | Write the agent's notes and call summary into the record's comments |
AI Alert Settings | Live-transfer and callback push alerts (with recipient lists) and an optional callback task |
AI Availability / Ping | Availability alert recipients and timeout |
Each section has its own Save button.
10. How iAssist Works
One submission, everything at once. The web agent sends a single submission containing the patient's details and — only when the patient completed one — the PAA. There is no second call: iAssist looks at what arrived and acts per your Record Creation Mode. If no PAA data is included, no PAA is ever created.
PAA details. PAA fields use the same format as iScreen (including the Medications, Substances of Abuse, Treatment History, and Related Contacts sections), so the mapping conventions your team already knows carry over unchanged.
Web attribution. Marketing values sent by the web agent — utmSource , , ,, , , ,user Agen t , and simil ar — are captured automatically into the Web Traffic section on the Lead and the Opportunity. Existing Web Traffic fields (such as and ) are reused, not duplicated.
Endpoint for the integration team. RVK submits to your instance's dedicated iAssist address ( ) with the API key from Section 4 inside the request. The exact field names come from your Field Mapping screen.
11. Frequently Asked Questions
Q: Does enabling iAssist change how iConnect or iScreen behave?
No. iAssist is fully independent — its own key, its own settings, its own mappings. The only shared piece is the PAA sub-table mappers (see Section 7), which both agents read by design.
Q: How do I switch a customer off iAssist?
A Dazos administrator unticks the iAssist switch in Admin → AI Agent Settings → Instance Mapping. The tab disappears and the endpoint immediately rejects requests.
Q: What happens if a submission arrives without a PAA in "Convert Only on PAA" mode?
The patient is kept as a Lead (with the "no PAA" Lead Status you configured, if any). If a later submission for the same person includes a PAA, the existing Lead is converted rather than duplicated.
Q: Do I have to set all the status/stage dropdowns?
No — every selector is optional. A blank selector means iAssist leaves that status or stage untouched.
Q: A PAA section (e.g. Medications) is showing empty rows or missing values — why?
Almost always a field-mapping gap: open the matching sub-table mapper and confirm each incoming field name is mapped to the right column. Values arrive under the same names iScreen uses.
Q: Can I rotate the API key?
Yes — generate a new key any time (Dazos admins only) and give it to RVK. The old key stops working as soon as the new one is saved.
Q: Who gets assigned the new records?
Whatever you set in User Assignment: Round Robin cycles through your selected users; Specific User assigns everything to one person; if neither is configured, a system integration user owns the records.
Need Help?
If you run into issues:
Check that iAssist is enabled for the instance (Active badge in Admin → Instance Mapping) and that the API key in the request matches the one on the settings page.
Re-check the Field Mapping and sub-table mappers for the fields that aren't populating, then resend a test submission.
Contact Dazos support with the approximate submission time and reference CRM-3355.