Mobile-first inputs
The keyboard adapts to the question.
Numeric keypad for amounts. Email keyboard for emails. URL keyboard for websites. Form-grade mobile input UX — inside an agentic AI chat where most competitors ship one generic composer.
What changes, based on what
Wengrow's agent has a field-aware state machine. When it knows it's collecting a typed field, the widget sets the HTML5 inputmode and type so the OS picks the right soft keyboard.
| Question type | Mobile keyboard | How it's wired |
|---|---|---|
| Currency / dollar amounts | Numeric keypad with , and . | inputmode="decimal" |
| Year / integer | Numeric keypad | inputmode="numeric" |
Email layout with visible @ | type="email" | |
| Website / URL | URL layout with visible .com | type="url" |
| Phone | Tel keypad | type="tel" |
| Postal / ZIP | Numeric keypad | inputmode="numeric" |
No custom keyboard. No overlay. The OS renders its native keyboard for that input mode, which means user layouts, languages, and accessibility settings keep working.
Why it matters on mobile
On iOS, the hit area of a key is 471% larger on the numeric keyboard than on the traditional keyboard (209 × 108 pixels vs. 52 × 76 pixels). Smashing Magazine, citing Baymard.
Three more numbers worth keeping in mind when you audit your forms:
- Auto-fill helps people fill out forms 30% faster. (Google, via Smashing.)
- The average checkout contains almost 15 form fields. Baymard research suggests most online services could reduce the number of fields displayed by default by 20 to 60%.
- Conversational forms show a 40% higher completion rate versus traditional forms, per Sendbird.
Those gains compound. Wengrow pairs the conversational format with the right keyboard for the right field — the two biggest mobile-form wins in one UI.
Why most agentic AI chatbots skip this
Static conversational form builders (Typeform, Tally, Landbot, Typebot, HeyForm) have been adapting keyboards for years — the field type is hardcoded into each step, so the right inputmode is trivial to set.
Agentic AI chatbots are different. The composer sits between the user and an LLM, and the UI doesn't usually know what kind of answer the model is waiting for. So the default is a single free-text composer: Intercom Fin, Zendesk AI, Ada, Drift, Sendbird, Chatbase, HubSpot AI, Voiceflow, Botpress — same pattern.
Wengrow's agent publishes its current field intent back to the widget, which sets the right input mode before the user starts typing. It's not new technology — it's the discipline of wiring form-grade input UX through an LLM-driven conversation.
We can't find another agentic chatbot doing this.
Works with the native OS keyboard
No custom keyboard, no overlay, no input hijacking. The widget sets the standard inputmode and type attributes and lets the OS pick the layout. That means:
- iOS Safari and Android Chrome — verified.
- User layouts, languages, and a11y settings — preserved (system font size, contrast, keyboard customizations all continue to work).
- Fallback behavior — if the device doesn't support a mode, the visitor gets the standard QWERTY. Nothing breaks.
- OTP autofill on iOS — supported for one-time codes (iOS-specific, as Apple defines it).
Also helps on desktop
On desktop the keyboard doesn't change, but the same typed-field intent drives validation: email fields check format, URL fields check scheme, phone fields enforce digits. Bad data doesn't make it to your CRM.
Adaptive mobile keyboard FAQ
Form-grade input UX, in an AI chat.
The keyboard adapts so visitors don't mistype. Leads land in your CRM with validated email, phone, URL, and amount fields — straight from the conversation.