FormantAI
Outbound calls that talk back.
Not a recorded broadcast. A two-way call that handles the objection, captures the outcome and logs it.
Trigger. Call. Outcome.
- 01 · Trigger
Your system decides who to call.
A due date, a lapsed policy, a new lead, a fresh COD order — fired by webhook or a scheduled list.
- 02 · Check
Rules before the dial.
Permitted hours, consent and preference, attempt limits and the right number type — checked before the call goes out.
- 03 · Converse
A real conversation.
Disclosure first, identity verified, facts read from your systems, objections handled as designed branches.
- 04 · Outcome
Written back, followed up.
Promise date, payment link, booking or callback logged to your CRM; a human gets the call if it needs one.
Outbound journeys that work best
- Collections: pre-due nudges, bounce follow-up, early buckets — see sample collection scripts.
- Renewals: every policyholder before the grace period — see renewal reminder templates.
- Lead callbacks: web and campaign leads called within a minute, qualified, advisor booked.
- KYC: explain what is due, send the V-KYC link, follow up until complete.
- D2C: COD confirmation, address fixes, reorders.
Outbound AI calling and the rules
Outbound is where regulation bites. Service and transactional calls (reminders on an existing loan or policy) are treated differently from promotional calls under TRAI's commercial-communication rules; promotional calls need consent and must respect the customer's DND preferences. Collection calls also follow RBI conduct rules, including permitted calling hours. Read TRAI calling rules and RBI recovery agent guidelines.
FormantAI checks these per call and per turn and keeps a full audit log. Sales calls run only to leads who asked to be contacted, or with recorded consent.