Requests
Some visitors are not asking for support — they are deciding whether to buy. Request capture lets Minaya notice that, offer to arrange a call, and record who they are alongside the conversation that led there.
How a request is captured
Minaya is given a tool it can call, not a keyword list. It decides from the conversation whether someone is showing buying interest, which means it works in every language the widget supports and for phrasings nobody thought to enumerate.
- A visitor asks about pricing, a plan, a demo, availability, or how to get started.
- Minaya answers the question first, then offers to arrange a call with your team.
- If they accept, it asks when suits them and for an email address or phone number.
- The lead is recorded and emailed to you, and Minaya confirms in its own words.
What it will not do
A widget that interrogates every visitor for contact details is worse than one that captures nothing, so the assistant is told to:
- Ask once. If the visitor declines or ignores it, the subject is dropped and never raised again.
- Never invent details. Only what the visitor actually typed is recorded — no guessed emails, no assumed availability.
- Leave support alone. An existing customer asking a routine question is not offered a sales call.
- Never interrupt. The question gets answered before anything is offered.
What a request contains
Contact details are only half of it. Each lead keeps the reason it exists:
- Email address, phone number, or both — whichever they gave.
- A one-line summary of what they were interested in.
- The specific product or plan they named, when they named one.
- When they said they are free, in their own words — “Tuesday after 5pm” — with their timezone, so that reads correctly.
- The conversation up to that point, with the message that triggered capture highlighted.
Availability is kept as free text rather than a calendar slot on purpose: parsing a stated preference into a timestamp loses the nuance and invites bookings the visitor never agreed to.
Turning it on
Request capture is included in every paid plan — it is not a separate add-on. The free tier does not have it.
It is also off by default on paid plans, including for existing widgets: it changes what your assistant says to visitors, so it is never switched on underneath you. Enable it under Widget appearance.
If a subscription lapses, capture stops but the requests already collected stay readable — those were paid for.
Setting the widget’s behaviour to Sales Agent turns capture on regardless of this toggle — a sales behaviour that never asks for contact details cannot do its job. With Assistant, Minaya still records a request when a visitor asks to be contacted; it just never raises the subject itself.
Tell it what you sell in the same place. That single sentence is what lets it tell a buying question from a support one, so it is worth being specific: “project management software for construction firms” works better than “software”.
New requests are emailed to the address you set, falling back to your handoff address and then to your account email.
Working the pipeline
Every lead starts as new and can be moved through contacted, qualified, won or lost, with private notes as you go. The Requests page filters by status and shows the counts, so what is still open stays visible.
Requests and handoff
The two are different intents and can run independently. Handoff is for a visitor the assistant could not help; a request is a visitor it helped who is interested in buying. A business often wants both.