Let your customers create a VayaPin in 90 seconds.
A mobile-first signup page your agent hands to a customer the moment they need a precise delivery location. Name, location, done — no app to download, no address to type, your brand throughout.
Pending session 5.8 (end-to-end submit) real capture
Three steps, one tap to finish
Your agent reserves a VayaPin and texts the customer a link. They land on a page that already knows who they are — all that's left is to pin the exact spot.
Confirm the pin name
5.3 component
(pending 5.8)
The page opens pre-filled with the VayaPin your agent reserved — the customer just confirms or picks an available alternative, checked live.
Drop the exact spot
5.4 + 5.5
(pending 5.8)
A Google Map centred on their location. Move the pin, and the street address fills in by reverse-geocode — formatted for their country.
Sign in & finish
5.6 + 5.7
(pending 5.8)
One-tap Google Sign-In ties the pin to the customer. Your system receives a webhook — and the customer gets app-store links to enrich it later.
Not another "download our app to continue"
Most location-capture flows lose the customer at the app-store wall. This one never leaves the browser.
| Typical app-download flow | VayaPin Consumer Signup | |
|---|---|---|
| To get started | Install a native app | Open a link — nothing to install |
| On a slow connection | 10–40 MB download first | Lightweight page, loads fast |
| Address entry | Type it out, hope it's right | Pin on a map, auto-formatted |
| Branding | The app vendor's brand | Your brand, your domain |
| Your system finds out | Polling / manual export | Webhook the moment it completes |
Two ways to turn it on
Run an agent that takes orders? Enable it in the dashboard. Building your own product? Wire it through one tool call.
Enable end-user pin creation
No code. When your agent meets a customer who has no VayaPin yet, it sends them the signup link — and you get the finished location back.
- Your agent calls
confirm_pinwith a suggested name and the customer's phone or email. - VayaPin texts the customer a link to
vayapin.app/signup/<rid>. - They complete the 3-step flow on their phone.
- You receive a
pin_createdwebhook with the full delivery payload.
One tool call from your agent
The same confirm_pin tool from the MCP reference. Reserve a pin, send the link, wait for the webhook — no address-handling code of your own.
“This customer has no VayaPin. Reserve one as BB:SUNSET and text the signup link to +1‑246‑555‑0142.” # agent calls: confirm_pin({ name: "BB:SUNSET", channel: "sms" })
{
"event": "pin_created",
"pin": "BB:SUNSET",
"location": {
"lat": 13.0789, "lng": -59.6018,
"address": "Sunset Crest, St. James"
}
}confirm_pin is one of the eight tools in @vayapin/mcp. The signup page is where that link lands.Tested on the devices your customers actually use
Every flow below was driven end-to-end against the live page before launch.
Safari · iOS
iPhone
Chrome · Android
Pixel
Slow 3G
throttled
Reverse-geocode
BB · GB · US
On the roadmap
Apple Sign-In
A second one-tap identity option alongside Google, for customers on iOS.
SMS & email verification
Full Twilio + SES verification once provider credentials are provisioned — today the page degrades gracefully when they're absent.
More languages
Localised copy and address formats beyond the current set.
Read more, then turn it on
What shipped
The release notes for Consumer Signup.
The story
Why we built a no-download signup flow.
How to enable
Wire it in with one tool call from your agent.
Links point to live docs pages today; the signup-specific changelog (P.1), blog post (P.2) and help guide (P.3) are swapped in when they publish.
Turn on Consumer Signup
Enable it in the dashboard, or have your agent call confirm_pin. The link does the rest.