What Roonly writes to your CRM
After every analyzed call or door visit, Roonly finds or creates the contact and logs a factual note with the outcome, duration, summary, and recording link.
Which CRMs
Roonly writes directly to your CRM with no middleware. FieldRoutes and JobNimbus are live and verified against real accounts. Connect either one under Integrations, then CRMs. Using something else? Roonly builds direct connectors on request.
Connecting takes a credential from your CRM admin: an API key for JobNimbus, or an authentication key, token, and a note type for FieldRoutes. Roonly verifies the credential, discovers the options it needs from your account, and saves the connection.
What gets written
After every conversation Roonly analyzes, a phone call in the office or a door or service visit in the field, it logs one note on the matching customer record. The note contains:
- A heading with the kind of conversation, who handled it, and when. Calls the AI receptionist handled are credited to it.
- The outcome and the call or visit duration.
- A factual summary of what was discussed: what the customer asked for, what was promised, prices quoted, access or pet notes.
- A link back to the recording and analysis in Roonly.
Scores, coaching, and feedback never go into the note. CRM notes are readable by everyone in your office, and coaching belongs to the person who took the call.
Find or create
Before writing, Roonly looks for the customer: first by the key Roonly stamped on a record it created earlier, then by phone number, then by first and last name with the address as corroboration. If it finds a match, the note goes on that record.
If nothing matches, Roonly creates a record only when it has a phone number, a street address, or a GPS position to tie it to; a name alone is never enough. Phone calls create the contact when the caller's number was captured. Door visits create a record only for the outcomes you allow, by default lead and callback. A no-interest knock never creates anything. Sales are matched to the record your rep entered rather than created twice, and Roonly keeps retrying that match for two days after the conversation.
New records carry the phone, the address, and the GPS position when the conversation has one.
What it does not change
Writeback is notes only. Roonly does not advance pipeline stages, change statuses, overwrite fields, or delete anything. Every write is additive, and every note is tagged with the conversation it came from, so the same conversation is never written twice.
Modes and the write log
Every connection starts in shadow mode. In shadow, each would-be write is staged in the write log with the match it found and the exact note text, and nothing touches your CRM. Review a few days of real traffic, then switch to live from the vendor row on the Integrations page. Field and phone can be set separately, and off stops writes entirely while leaving reads for campaigns intact.
The Integrations page shows the last successful write and the last error for each connection. The CRM Log page under Office lists staged and completed entries. To backfill a past conversation, open it and use Sync to CRM.
Retries
A failed write does not consume its slot. Roonly retries failed writebacks every 30 minutes for up to 48 hours, so a CRM outage or a rate limit does not silently drop a note.
Related
Still stuck? Contact support.