How it works
Actions and approvals
The agent can do things, not just answer. You decide which ones need a human to confirm.
What happens
- When a conversation calls for an action, the agent uses a connected tool: book the meeting, create the CRM contact, file the ticket, run the report.
- Any tool can require an approval card before it runs. The agent proposes the action in the chat, and either the visitor or your team confirms it in a card.
- Approval can be forced per tool, or left to the agent’s judgment for low-risk reads.
- Actions that need the visitor to be signed in show a login gate card first.
What your customers see
- Structured cards in the chat: available time slots, an appointment to confirm, an approval to give.
- The receipt afterwards: a booked slot, a contact in the CRM, a ticket number.
What NeevAI does for you
- Decides with you which actions the agent may take on its own and which need approval.
- Tests every action end to end before it goes live, and watches the first real ones.
The honest limitation
Actions run when a conversation asks for them. Scheduled or unattended runs, where the agent acts on its own on a timer, are on our roadmap and not available today.