Calls Related — Triggers & Actions
Use RepForce.ai triggers and actions to connect your AI calling flows with automation—personalize conversations in real time and drive follow-ups automatically.
What Are RepForce Tools?
RepForce tools are the building blocks that connect AI calls to your business systems. They enable real-time data exchange, personalized dialogue, and automated post-call tasks.
Where To Configure
Open Automate Platform → create a flow → choose a Trigger (how the flow starts) and add Actions (what the flow does). Map variables and set timeouts.
- Select trigger (Inbound or Call Ended)
- Add actions (Return Variables, Add Lead, Send SMS, etc.)
- Map data and test
Triggers
Inbound Call — Variable Injection
Fires before the AI answers an inbound call. Use it to fetch customer context and return a JSON payload that gets injected into the AI’s prompt.
- Personalize tone, language, and business rules
- Define flags and routing preferences
- Set conversation parameters (max hold, transfer rules)
Configuration
- Select Inbound Call as the trigger
- Fetch data (CRM, billing, eligibility)
- Return variables as JSON (see example)
Performance: aim for ≤ 2s. Provide sensible defaults if lookups fail.
Call Ended
Fires right after the AI call completes. It includes transcript, extracted variables, outcome, duration, numbers, and technical metadata—ideal for logging and CRM updates.
What You Get
- Full transcript with timestamps
- AI decisions, outcomes, and sentiment
- Recording URL (if enabled)
Actions
Add Lead to Campaign
Create a lead from external sources (Sheets, HubSpot, Facebook Leads, etc.) and assign it to a specific AI campaign.
- Select the target AI campaign
- Map contact fields (name, phone, email)
- Add attributes for future call context (e.g.,
source=fb_lead,priority=high)
Return Variables
Return a structured JSON to the AI for live personalization during inbound calls.
Match your prompt schema and keep keys consistent for reliable behavior.
Send SMS
Send confirmation messages, reminders, links, or quick updates—using SMS-capable numbers.
- Keep messages concise and professional
- Include opt-out text if required by local laws
- Test deliverability before large sends; monitor delivery rates and cost
Note: SMS availability depends on region/number type. Contact support if unsure.
Best Practices
- Variable Injection Performance: keep pre-answer enrichment ≤ 2s
- Data Structure: follow your prompt schema; validate JSON; document custom fields
- Error Handling: provide fallback defaults; log failures; monitor response times
Quick Recipes
Personalized Greeting on Inbound
- Trigger: Inbound Call
- Lookup: CRM by caller phone
- Action: Return Variables with
customer.nameandpersona - Prompt: “Greet the caller by name and confirm intent.”
Post-Call Summary Text
- Trigger: Call Ended
- Extract:
summaryvariable - Action: Send SMS with summary + link
FAQ
How do I inject customer context before answering?
Use Inbound Call — Variable Injection and return JSON that matches your prompt schema.
What arrives with the Call Ended trigger?
Transcript, variables, outcome/sentiment, duration, and numbers; recording URL if enabled.
Can I text a caller automatically after a call?
Yes. Chain Call Ended → Send SMS with a template that includes opt-out language if required.
