CRM and automations
The documents you review already carry your client data. ArcMichael proposes CRM records from them, your admin confirms, and the automations run from there.
Extracted, then confirmed
After a review, ArcMichael proposes clients (including joint applicants), contact details, addresses, the case, and the products: lender, rate type, rate-end date and balance for a mortgage; insurer, premium and review date for a policy. Nothing is written to the CRM until the admin confirms or edits it, and every confirmed value keeps a pointer to the document it came from.
Triggers
Product end date
A fixed rate ending in 180, 120 or 90 days. The remortgage conversation starts before the lender's letter does.
Policy review date
A protection policy due its review.
Birthday
A short, personal message on the day.
Completion anniversary
One year in the new home.
Case completed
The thank-you, and the review request.
Review shared
The adviser is told a report is waiting.
Channels
Messages go by email, and WhatsApp once Meta has approved our templates, with SMS as a fallback. Email is sent through Resend. WhatsApp uses the Meta Cloud API with approved templates; each template shows its category (utility or marketing) and its per-message cost before you activate an automation.
Consent per contact
Every contact has a consent record per channel: the lawful basis (service message, legitimate interest with the PECR soft opt-in, or explicit consent), how it was captured, when, and any withdrawal. Marketing messages are sent only to contacts with a recorded basis; ArcMichael refuses to send otherwise. Service messages, such as a rate ending in 90 days, still honour an opt-out. Suppression lists apply across channels.
Send windows
Sends happen inside a window you set, 08:00 to 20:00 UK time by default, never on a client's marked quiet days, and once per client per trigger per period, so a re-run never sends twice.