ZapBounce and Retool
Retool builds internal tools, which means the person typing an address is a member of staff rather than the customer. That changes the right interaction.
A customer mistyping their own address will notice when nothing arrives. A staff member typing a customer's address will not, and neither will the customer.
Staff typing customer addresses have no feedback loop
When a support agent enters a customer's address from a phone call, nothing in the process tells them they misheard it. The confirmation email bounces into a queue nobody reads.
The customer then calls again about the thing they never received, and the agent re-enters the address, sometimes the same way.
A verification call on field blur, showing the verdict and the typo suggestion in the interface, closes that loop while the agent still has the customer on the line.
How the data moves
Add a REST API resource for the verify endpoint
Retool resources hold credentials server-side, so the key never reaches the browser.
Trigger the query on blur, not on submit
The agent has moved on from the field and the result arrives before they finish the form.
Show the verdict inline, and the suggestion
A badge next to the field, plus the did_you_mean value as clickable text. Never apply it automatically.
Warn rather than block
An internal tool that refuses to save is an internal tool people work around. Show the warning and let the agent decide.
Setting it up
- Create a REST API resource in Retool pointing at the verify endpoint with the key in a header.
- Add a query triggered by the email field's blur event.
- Render the verdict as a colored badge beside the field.
- Show the did_you_mean value as a clickable suggestion the agent can accept.
- Allow the save regardless, storing the verdict alongside the address.
- Log verdicts so you can see which agents or workflows produce the most bad addresses.
Retool: common questions
Should the save be blocked on an invalid verdict?
No. Warn, store the verdict, and let the agent decide. A blocked save in an internal tool gets routed around.
Where does the key live?
In the Retool resource, which keeps it server-side. A key in a JavaScript query reaches the browser.
On blur or on submit?
Blur. The result arrives while the agent is still filling the form, which is when the correction is free.
Check a Retool export today
100 free checks a month, no card. Unknown results and duplicates are never billed.