boberdoo setup

How it works on boberdoo

boberdoo calls third-party APIs during ping and post processing through its Outside Services tab, the same bring-your-own-credentials mechanism behind its Real Phone Validation, IPQualityScore, and Anura integrations. Outside services run as a lead is processed and can reject it with a custom response, and inbound calls are processed with the same business rules as web leads.

The Outside Services list is curated by boberdoo rather than self-serve, so wiring CallerSift in is a support request, not a settings page: boberdoo's own docs say to open a ticket and their team will integrate the service into your tab.

What to send boberdoo support

1. Your lookup URL from the dashboard home page: POST https://api.callersift.com/v1/your-workspace.
2. The request contract: body field caller_number (E.164) plus api_key, or the key in an X-Api-Key header. Form-encoded and JSON both work.
3. The decision contract: the JSON response field verdict is "allow" or "block"; treat block as a reject and let allow flow through unchanged.
4. The safety rule: on timeout or error, process the call as allow. A screening outage must never drop a genuine caller.

Ask boberdoo to attach the service to your phone campaigns (noPingRing matching runs when the call physically arrives, per their call routing docs), and verify the reject path on a test call before going live.

Official boberdoo docs

1. Outside Services integrations: the mechanism and the open-a-ticket path for custom services.
2. Outside Services support: tab overview and walkthroughs.
3. Call routing: inbound calls processed with lead business rules.
4. Phone campaigns: campaign setup, caller ID checks, and the default number fallback.