Plan requirement
| Subscription | x-bees Standard or higher, UC-Business or higher (Collaboration 7) |
| Access | WMS administrator |
When nothing off the shelf fits, a webhook or a popup URL connects Wildix to your own system with very little work.
Two approaches
- Popup URL. A call arrives and a page of your choosing opens, with the caller's number in the address. Your system does the lookup and shows the right record.
- Webhook. Wildix sends call events to an address you control, and your system decides what to do with them.
Start with the popup URL
It solves the most common request, which is "show me the customer when they call", and it usually needs nothing more than a URL that already exists. If your system has a search page that accepts a phone number, you are most of the way there.
When a webhook is the better fit
When something should happen without anyone looking at a screen: logging to a system of record, triggering a workflow, updating a dashboard. Webhooks fire whether or not a person is watching.
Numbers arrive in international format. If your database stores them locally, normalise before matching or nothing will ever be found. This is the single most common reason a custom integration appears not to work.
Setting it up
Both are configured in WMS under integrations. The Wildix side is straightforward; the work is on yours, deciding what to do with the number or the event.
If you are not sure which fits, describe what you want to happen and we will tell you which one to use.
Comments
0 comments
Article is closed for comments.