Answer with the source
The fact and where it came from.A short card shows the answer from your connected documents, the file and the page, and when it was last updated. You decide whether to use it.
For sales engineers and solution consultants. When a prospect asks about versions, integrations or limits, Ajenzo looks in your own documentation and shows the answer with its source, so you don’t have to promise a follow-up email.
Business allows 600 requests per minute.
On Business it’s 600 requests per minute. If you need more, Enterprise sets the limit per contract.
API reference v3.pdf · page 12
Technical buyers test the details. The answer usually exists somewhere: in release notes, a security questionnaire or a call from last month. Finding it during the call is the hard part.
“Does version 4.2 support single sign-on?”Release notes and the product matrix
“Which data centre region do you use?”Security documentation and earlier answers
“Can we connect it to our ERP?”Integration guides and partner lists
“What did your colleague say about the API limits?”An earlier conversation with this prospect
Example questions. The cards on this page are illustrations.
A short card shows the answer from your connected documents, the file and the page, and when it was last updated. You decide whether to use it.
When something said conflicts with your sources, such as a version, a limit or a price, the difference comes into view.
Decisions, follow-ups and unanswered questions come together when the conversation ends, ready for your follow-up.
Release notes, specifications, API references and security documents as PDF, Word or text.
What the prospect said last time, so you can pick up the thread.
A read-only connection through MCP or an API key, for example to an internal knowledge base.
Connect your knowledge and stay with the person in front of you.