📩 Send Custom Event to Contact Profile
Fire a custom event from your AI Agent onto a Regal contact profile mid-conversation
Overview
Custom Events unlock powerful new capabilities for your AI Agents. With just a simple custom action, you can push important conversation updates onto a contact profile — fueling better agent handoffs, journey triggers, and reporting.
This guide will walk you through exactly what Custom Events are, when to use them, and how to set one up — even if you’re not a developer!
What Does This Custom Action Do?
This custom action sends a new event onto the contact's profile while the AI conversation is still happening.
It’s perfect for mid-call workflows, like:
- Warm transfer handoffs:
Send a quick call summary to the human agent before connecting the customer. - Journey triggers:
Start a new Journey based on milestones in the conversation (e.g., appointment booked, quote delivered). - Custom reporting:
Log conversation breadcrumbs (like “customer got to qualification complete moment”) for analytics.
Tip:
Think of a custom event like dropping a little “bookmark” inside a contact’s record, exactly when something important happens.
Key Use Cases
Use Case | Why It’s Powerful |
---|---|
Pre-transfer Summary | Help human agents see what the AI has already handled. |
Appointment Reminders | Trigger an SMS confirmation journey automatically. |
Custom Analytics | Capture micro-events inside the conversation (quote given, consent obtained, etc.). |
Live Contact Updates | Instantly update contact traits mid-call for real-time insights. |
Prerequisites
Before you can send a Custom Event, you’ll need:
- 🔑 Your Regal API Key
If you have trouble finding this ask [email protected]. - 🤖 AI Agent Configured for Custom Actions
You’ll set up a Custom Action that the agent can call at the right moment.
Setting Up the Custom Action in Regal
Setting up your custom action is quick:
- Create the Action
In the Regal AI Agent Builder: → Add Action → Custom Action

Example: Sending A Summary to the Transfer Agent
- Fill Out the Details
Field | Example |
---|---|
Name | send_summary_to_transfer_agent |
Description | Call this function to send a call summary to the agent before initiating the transfer |
Endpoint URL | https://events.regalvoice.com/events |
Define AI Variables | call_summary (string) | customer_questions (string) | sentiment (string) |
Custom Header | Authorization: YOUR API KEY GOES HERE |
Payload | See JSON Template Below |
You’ll use simple handlebars syntax for variables like {{variables.call_summary}}.
👉 Screenshot Example Setup:

Example: Variables sent to the Human Agent Prior to Transfer
JSON Payload Template
You’ll define the payload directly inside the Custom Action. Here’s an example:
{
"userId": "{{contact.externalId}}",
"traits": {
"phones": {
"{{contact.contactPhone}}": {}
}
},
"name": "AI Agent Call Summary",
"properties": {
"ai_agent_name": "<Your Agent Name>",
"call_summary": "{{variables.call_summary}}",
"customer_questions": "{{variables.customer_questions}}",
"customer_sentiment": "{{variables.sentiment}}"
},
"eventSource": "Regal Voice"
}
⸻

Example: Payload to Send A Summary to the Transfer Agent
What to Update:
- Replace the API key placeholder with your own.
- Map your AI variables properly.
Tip:
You can customize the properties section with any additional details you want Regal to track, such as appointment time, product type, or notes!
Test Your Custom Action
Testing is simple:
1 - Save your Custom Action inside the AI Agent.
2 - Trigger the action during a test call or simulated flow.
3 - Verify that the event appears inside Regal’s Recent Events Explorer.
4 - Check the payload is correct and no fields are missing!

Example: Pre-Transfer Summary Event in Recent Activity
5 - Configure your custom event to display in the Agent desktop for the approach agent team(s). See docs for how and then check that you see it displayed on the Activity desktop

✅ If everything is good, you’re ready to use it in production.
Troubleshooting & FAQ
Problem | Solution |
---|---|
401 Unauthorized | Double-check your API key in the Authorization header. |
400 Bad Request | Validate your payload against Regal’s Event API schema. |
No event shows up | Ensure your agent is calling the right Custom Action and the public URL is correct. |
FAQ
Can I send multiple events during a call?
Absolutely. You can call this Custom Action multiple times wherever needed! Just include instructions in your prompt for when the agent should call the action.
Can I hardcode properties instead of relying on AI variables?
Yes — hardcode any constant properties inside the Payload Format field.
Do I need to host anything?
No external hosting or code deployment needed! Everything happens inside Regal's no-code Custom Actions setup.
🙋♀️ Need Help?
If you need help setting up your custom event—or you’d like a Regal AI Expert to review your setup—reach out anytime at:
We’re happy to help!
Updated about 1 month ago