Notifications and delivery
Notifications bring call results to people and tools that handle the next step. Configure destinations in Settings → Notifications under Call notifications and send a test before using them for customer work.
Choose a channel
Section titled “Choose a channel”| Channel | Best use | Before enabling |
|---|---|---|
| A readable summary and dashboard link | Check the recipient and spam filtering | |
| SMS | A short alert when attention is needed | Verify the destination and obtain appropriate permission |
| Slack | Team visibility in a chosen workspace/channel | Confirm channel access and plan availability |
| Webhook | Structured events for your own workflow | Verify signatures, deduplicate IDs, and restrict endpoint access |
To connect Slack, choose Connect Slack. You can paste an incoming-webhook URL that a Slack workspace admin created for the channel, or use Add to Slack when it is offered. A pasted URL must be a Slack hooks.slack.com address; Xaller.ai sends a sample message and saves the connection only after Slack accepts it. Paste a new URL to reconnect.
Slack is included in the launch Growth and Pro catalog. Only use options available in your account. A plan allowance does not mean every external integration has been released.
Set filters and content
Section titled “Set filters and content”Choose which outcomes or conditions trigger the destination. Avoid sending every test call to a busy operational channel. Decide how much information the recipient needs; full summaries can contain personal information.
Use a minimal payload when the receiving system needs a signal and dashboard link rather than caller details. Keep destinations current when a person leaves or a phone number changes.
Send and inspect a test
Section titled “Send and inspect a test”Use the integration’s test action, confirm receipt, and inspect the delivery log. Then make a controlled call that matches the filter and check the real result. A successful authorization alone does not prove delivery works.
Text replies and email bounces
Section titled “Text replies and email bounces”If a recipient replies STOP to a text alert, that number shows Opted out by text reply and receives no more texts until they reply START. When no number on an SMS destination can receive texts, the account owner gets that call notification by email instead, with a note explaining why.
If an email address bounces permanently, it is marked as bounced and stops receiving notifications until you correct it. A recipient who reports a notification email as spam is opted out.
Emails about your account, such as onboarding tips and the weekly summary, are separate from call notifications. Choose them in Settings → Notifications under Emails from Xaller, or with the unsubscribe link in any of those emails. Security, billing, and account emails always arrive. Emails from Xaller.ai lists every category.
When delivery fails
Section titled “When delivery fails”Check the delivery status and error, destination spelling, revoked permissions, disabled integrations, channel access, and recipient filtering. Fix the destination before retrying. Repeated failures can pause delivery; after correcting the cause, check whether the integration needs enabling again.
Webhook receivers should respond promptly with 2xx after accepting the event and handle repeated delivery IDs safely. See the webhook reference for payloads and signature verification.