Skip to main content
A lead box is a notification subscription on a Mav.next agent. It picks a set of events you care about — a contact getting qualified, a phone call transferring to a rep, a policy being sold — and pushes them to a webhook URL or an email address as they happen. Use lead boxes to keep your CRM, dialer, or team inbox in sync with what the agent is doing, without polling.

​
How it works

Every lead box has three parts:
  • Agent — the agent whose activity you want to hear about. Lead boxes are per-agent, so you can subscribe different destinations to different agents.
  • Events — one or more events from the event catalog. Leave everything unchecked to subscribe to all external events.
  • Destination — either a Webhook (HTTPS endpoint that receives a JSON POST) or an Email address that receives a formatted message.
Each event is delivered independently the moment it fires on any contact that agent is working.

​
Adding a notification

1

Open the agent

From Agents, open the agent you want to hear about.
2

Add a notification

In the agent’s settings, click Add notification to open the notification dialog.
3

Pick events

Check the events you want to receive from the event catalog. Leave them all unchecked to receive every external event.
4

Choose a destination

Pick Webhook and enter an HTTPS endpoint (optionally with a Bearer token), or pick Email and enter a destination address.
5

Save

Save the notification. It takes effect immediately for new activity on that agent.
You can add as many lead boxes as you need to a single agent — for example, one webhook that receives every event for your data warehouse, plus an email that only receives sold for your ops team.

​
Webhook destination

Webhook deliveries are HTTP POST requests to your endpoint with a JSON body describing the event and the contact it happened on. The payload shape matches the outbound webhooks reference — activity_type, activity_label, contact identifiers, and originator data.
Endpoints must be HTTPS. Mav expects a prompt 200 response — acknowledge the payload first and process it asynchronously.
Optional configuration:
  • Encoding — JSON (default) or form-encoded.
  • Auth — None or Bearer. When Bearer is selected, the token you provide is sent as an Authorization: Bearer <token> header on every delivery.

​
Email destination

Email deliveries are formatted messages sent to a single address. Use this for team inboxes and lightweight alerting where a webhook would be overkill — for example, notifying an ops address when a contact converts to Sold.

​
Editing and removing

Each notification appears as a row in the agent’s settings. Use the row’s edit action to change events, destination, or credentials; use delete to remove the subscription entirely. Changes take effect on the next event that fires.
If you run multiple agents, add the same webhook URL to each agent you want to hear about — subscriptions are per-agent, and this is how you fan a single downstream system across the account.

​
What you can subscribe to

The events available in the notification dialog are the external events in Mav.next — engagement lifecycle moments, phone-call lifecycle moments, and conversions. See the full list, along with what triggers each one, in the notification events reference.