Web callback form
Your visitors request a callback from your website — and it's as if they had dialed your number and were waiting in the queue, without staying on the phone. Same queue, same agents, same automatic callback.
It is not an email to your inbox, or a CRM entry to "call back when someone has time". The moment they submit, the person is in the phone queue.
Preview
Request a callback
Name + number → queue → agent callback
Public link or iframe — captcha included
What is it?
The web callback form is a lightweight page, published per call queue, that you display on your site via a link or an iframe. The visitor enters their name and number: at that instant, it's as if they had called and were waiting on the phone — except they don't have to stay on the line. The request is in your PBX, in the real queue.
Your agents see the request on the wallboard like a waiting caller. When their turn comes, the system dials their number — exactly like after a "press 1". See also the press 1 phone callback.
What most websites do
Lead → email → CRM → "we'll call back"
- ✕ An email lands in an inbox — someone has to read it
- ✕ Or a CRM entry waits for a salesperson to open it
- ✕ The customer isn't in any queue: nothing forces a callback now
- ✕ Risk of being forgotten, delays, "we'll call you back tomorrow"
With us
As if the customer were already on the phone
- ✓ The moment they submit, they are in your PBX queue
- ✓ Your agents see them like a waiting caller (wallboard)
- ✓ When their turn comes, the system dials their number — not a human who "remembers to call back"
- ✓ Same engine as the *1 callback: queue, agents, timeouts, alerts
How it works
Four steps — from your website to the conversation with your agent.
You enable the link
On a queue, enable the web form, choose the display DID (outbound Caller ID), then copy the URL or the iframe snippet.
The customer submits
On your site, they enter their name and number. A captcha limits spam — no waiting on hold.
They join the queue
The request joins the queue (end of line), visible like *1 callbacks: wallboard, agents, max wait times.
We call them back
As soon as an agent is available, the system dials their number using the chosen DID — a normal conversation.
Benefits for your business
- ✓ Fewer web drop-offs — the customer doesn't wait on the phone; they get on with their day while the queue moves.
- ✓ Like a real call on hold — not an email, not a CRM entry: the request is in the phone queue as soon as it's submitted.
- ✓ One queue, one team — agents handle web and phone together, no separate "web leads" silo.
- ✓ Simple integration — URL or iframe, no widget to develop on your end.
- ✓ Per-queue control — enable the web form independently from *1, with the DID and POP of your choice.
- ✓ Same supervision — wallboard, reports and expiry alerts also apply to web requests.
- ✓ Name shown to the agent — the name entered on the form is presented with the callback call.
Phone callback vs web callback
Press 1 (phone)
The caller is already in the queue. They confirm the callback, hang up and keep their FIFO position.
- • Ideal during a call surge
- • Spot usually kept (current position)
- • Offered in FR / EN / ES based on the queue language
Web form
The visitor hasn't called yet — but the moment they submit, it's as if they were already waiting on the phone (end of queue, same engine).
- • Not an email or a CRM entry
- • Public link or iframe
- • Captcha + built-in abuse protection
Use cases
Contact page
Offer "We'll call you back" next to your phone number, without a generic sales form.
Product / service pages
An interested visitor requests a callback without leaving the page — your team handles the request in the queue.
Campaigns & landing pages
Embed the iframe on a landing page: hot leads join your agent queue directly.
Adding it to your website
In the client portal, open the queue → Options → enable the web form / public link, select the DID, save. You immediately get:
Public URL
To share, put behind a button, or open in a new tab.
Iframe snippet
To paste into your CMS (WordPress, custom site, etc.) — lightweight forms built for embedding.
Included with our Cloud PBX — configured 100% in the portal, no server installation on your end.
Frequently asked questions
Everything you need to know about the web callback form and how it plugs into your queues.
What is a web callback form?
Is it the same as the "press 1" callback?
How do I add the form to my website?
Does the customer jump ahead of callers on the line?
Can I enable only the web form, without *1?
Which number does the customer see on the callback?
Is it protected against spam?
Is it just an email or a CRM entry?
Have another question about web callback?
Contact our teamGet a callback for your quote
Want the web callback form (and the PBX) for your business? Leave your details: an advisor will call you back with a tailored quote.
- 1 Briefly describe your situation
- 2 We call you back shortly
- 3 Receive a clear quote, no commitment
Ready to put your visitors in the queue?
Test the real form (phone queue), or request a quote to enable it on your queues.
Related solutions: Queues with *1 callback, Cloud PBX, business VoIP telephony.