It’s 4:10pm. You’re in the back of an Uber, on the way to a 4:45 customer meeting. You don’t need a desk. You need the Account 360 your team uses every day, on the phone in your hand, in voice or text, with the same Adaptive Card layout you’d see in the portal. The Henoyo mobile app is a thin client over your Henoyo install, paired by QR code in thirty seconds.
This quarter · late-beta iOS, closed-beta Android. Join the beta.
It’s 4:10pm. You’re in the back of an Uber to a 4:45 customer dinner with Acme. The driver took a route you don’t recognize and the ETA is now tight. You open the Henoyo app and tap the mic.
Sarah taps the mic:“Pre-call brief on Acme. I’m meeting Lisa Cho in thirty minutes.”
Twenty seconds later, the answer renders as the same Adaptive Card you see in the portal:
Henoyo through Mobile:Acme is your $1.8M renewal closing August 18. Lisa Cho is your champion. Last QBR was March 22 and went well. Net new ARR is up 12% year over year. Two open support tickets are aged 23 days; Marcus owns those and is likely to come up. The risk to flag: Lisa may push on pricing because Acme procurement is auditing all renewal quotes this quarter. The ask: don’t commit to a discount tonight; offer to come back with a multi-year structure on Friday.
You read the card on the way in. Lisa pushes on pricing. You acknowledge the audit, propose Friday for a multi-year structure, the dinner stays warm. The same Prompt you’d run from your laptop ran from your phone, against the same install, with the same audit trail your manager already trusts.
Three things, mostly.
Not the morning when you’re in front of your laptop. The cab on the way in. The customer floor before the meeting starts. The walk between the parking lot and the lobby. The phone is the device that’s actually with you, and the Account 360 lives there too now.
Tap to talk in the Uber when typing isn’t safe. Tap to type at the dinner table when speaking out loud isn’t. The same conversation thread continues across both, the way the same conversation continues across the portal and the app.
Open the portal at your desk, click Pair Device, scan the QR. The app talks directly to your install. Your data stays in your cloud, your CRM connection stays in your secrets store. There’s no Henoyo-cloud middleman, no second admin path, no second audit trail.
Most of the mobile apps you’ve installed at work over the last decade have been their own product. Their own data store. Their own log-in. Their own audit trail. Their own thing to keep updated, retire, audit annually, and explain to security every time someone joins the team.
The Henoyo mobile app isn’t any of that. It’s a UI for the install your team already runs in your cloud, the same way the web portal is. If your install is paused, the app shows that. If your install is upgraded with new Prompts, the app picks them up automatically. If a device is lost, your admin revokes the pairing token from the portal and the app stops working in seconds.
The app stores conversation history (so you can scroll back) and the structured Adaptive Card outputs (so they render fast on re-open). It does not store a local copy of your CRM. It is a viewer, not a database.
Three example invocations: voice or text, the response renders as the same Adaptive Card you see in the portal, audit trail in your cloud.
Pre-call brief on Riverbend. Meeting in twenty minutes.
Same Account 360 readout you’d get on Voice in the browser, rendered as an Adaptive Card on the phone. Spoken back through AirPods at the same time.
Read logged in your Henoyo audit trail under your user, with the device fingerprint of the paired phone.
Stuck deals, on the train Monday morning.
Adaptive Card with the three deals over $50k that haven’t moved in 14 days. Each card row links to the Salesforce record; tap-and-hold pins to your follow-ups for the day.
Read logged in your Henoyo audit trail; the pin action triggers a separate write to your Salesforce activity history.
Log next steps from the Acme dinner.
You dictate three follow-ups in the elevator. Henoyo confirms each one verbally and shows the structured write summary on screen before committing.
Write logged with user, before/after field values, and the dictation transcript. Lands on the Account record in your CRM.
Same Prompts, every surface.
Three answers, in case you’re forwarding this page to your mobile or device admin.
In your AWS or Azure account. The mobile app talks directly to your install over the internet. There is no Henoyo-cloud middleman in the request path. The pairing handshake is end-to-end between the device and your install. Tokens to your CRM stay in your secrets store inside your cloud account.
Every paired device shows up in your portal under Paired Devices with the user, the device fingerprint, and the last-seen time. Your admin revokes the pairing token in one click and the app stops working in seconds.
Standard Apple App Store and Google Play distribution. Manageable through your existing MDM (Intune, Jamf, or any MDM that supports the standard managed-app config protocols), no app-specific MDM configuration required. For BYOD environments, per-tenant policy can require pairing only from devices in your MDM, or restrict pairing to specific user roles. Your mobile admin sets the policy once; pairing attempts that don’t meet it fail with a clear message.
Both. Late-beta TestFlight on iOS, closed beta on Google Play. Public release is this quarter; demo accounts can join the beta now.
In the portal at your desk, click Pair Device. A QR code appears with a one-time pairing token. Scan from the mobile app. The app exchanges the token for a long-lived device token scoped to your user. The device shows up in your portal under Paired Devices, where it can be revoked.
No. The app caches conversation history and the structured Adaptive Card outputs so they render fast on re-open. It doesn’t keep a local copy of your CRM. Each Prompt run hits your install. If you uninstall the app or the device is wiped, no data is lost from your install. The app is a viewer.
Mostly no. You need a connection to run a Prompt because the model and your data are in your cloud. The app gracefully queues messages and shows your last conversation if connectivity drops, then sends queued messages when you’re back online.
By invitation only. Join the early-access list and we’ll send TestFlight (iOS) or Google Play closed-track (Android) invites in the order seats open. We’re not running a public TestFlight or an unlisted App Store track in this phase. Every device on the beta is one we know about, paired to a known install.
Join the beta. We’ll send you a TestFlight or closed-beta link, walk through the QR pairing, with your IT lead in the meeting if you want, and answer the questions your mobile admin is going to ask.