Questions teams ask before trusting an AI agent.

Personas is an AI voice and chat agent platform by DapurAI for frontline business conversations. It helps teams answer questions, qualify leads, collect visitor context, and hand off conversations when a human should step in.

It is most useful for businesses with repeated customer questions: clinics, hospitals, retail sales teams, service counters, schools, property teams, hotels, event booths, and companies that want a guided website assistant.

Personas is built around agent setup, uploaded knowledge, website embedding, voice conversation, lead capture, and live handoff. The goal is not only answering text, but helping a business manage real customer intake.

Yes for common setups. You create an agent, define its tone and use case, upload knowledge, test responses, then embed it or prepare the target channel. More complex deployments may still need technical support.

It can greet visitors, understand their intent, answer from uploaded knowledge, ask follow-up questions, collect contact details, summarize what the visitor needs, and trigger handoff when the conversation should move to a human.

Yes. A sales agent can ask about budget, product interest, timing, location, quantity, and other qualification points, then prepare a cleaner lead summary so the team does not start from zero.

Yes. Personas supports voice-style interactions for demos, kiosks, and customer-facing assistants where speaking feels more natural than typing.

Yes, the agent can be shaped to offer a helpful prompt after idle moments, such as suggesting common questions, asking what the visitor is looking for, or guiding them to support, sales, or health flows.

The agent is designed to search the approved knowledge base before answering. For teams with strict accuracy needs, the best setup uses clean sources, focused scope, and review of conversations that are unclear or high risk.

Personas sits inside the broader DapurAI ecosystem, so more custom workflows can be discussed as tailored AI projects: internal tools, document intelligence, operational assistants, or secure deployment needs.

Yes. Website embedding is one of the primary flows. A public widget can answer from your approved knowledge and collect visitor details before your team follows up.

WhatsApp rollout depends on the customer's business setup, provider configuration, and operational requirements. Personas can connect the conversation workflow once the messaging channel is configured for the deployment.

Review the intended number, account ownership, provider terms, message volume, handoff process, and operational responsibility before rollout. For production use, we recommend using a dedicated business number and documenting who owns the channel.

Yes. Personas supports voice-oriented experiences for demos, front desks, kiosks, branches, and booths where visitors benefit from quick spoken guidance.

You can use website URLs, FAQs, product catalogs, pricing notes, PDF or DOCX documents, SOPs, doctor schedules, service descriptions, and other approved business material.

The agent is designed to prioritize your approved knowledge and business context. For sensitive or unknown topics, the safer behavior is to clarify, say it does not know, or hand off to a human.

The platform is built with account ownership in mind so each user's agents, conversations, and knowledge are scoped to the right owner. This is especially important for multi-tenant usage.

Knowledge should be treated as maintainable business material. Teams can update sources when policies, schedules, services, or product information changes.

A human should take over for complaints, urgent issues, medical or legal judgment, payment disputes, custom pricing, edge cases, or anything requiring approval from your team.

Yes. Conversation history and handoff status help teams understand what happened, follow up with visitors, and improve the knowledge base over time.

No AI system should be treated as perfect. The best rollout uses approved knowledge, careful testing, handoff rules, and periodic review so risky or unclear cases are handled by humans.

Yes, Personas is shaped for Indonesian frontline usage and can support Bahasa Indonesia and common mixed-language conversations depending on the agent setup.

A simple website agent can be tested quickly once the knowledge source is ready. WhatsApp, enterprise security, custom workflow, or production handoff processes may require extra setup.

Pricing generally depends on channels, number of agents, conversation volume, voice usage, storage, support needs, and whether the project needs custom integration or managed deployment.

WhatsApp and messaging-provider costs may be billed separately depending on the selected setup, destination country, message category, volume, and provider terms. Personas pricing should be reviewed together with the operational messaging model.

Yes. A pilot is usually the best first step: choose one use case, prepare clean knowledge, test common questions, review failures, and only then expand to more channels or teams.