Revenue Inbox and agent-ready work

What is the Revenue Inbox?

The Revenue Inbox is a prioritised work queue for tasks that can protect or create revenue. Pivra creates recommendations from:

• new leads and quote requests;
• scheduled lead follow-ups;
• visitors waiting for a human;
• repeat service that is approaching or overdue; and
• failed deliveries to connected business systems.

Open Dashboard → Revenue Inbox to see the most important work first.

How priority works

Pivra uses transparent business signals rather than silently allowing an AI model to decide:

• live human handoffs are urgent;
• failed integration deliveries are high priority;
• overdue quote and service follow-ups rank above future work; and
• the configured average lead value appears as potential value, not guaranteed revenue.

Open any task to see Why this matters, its reason signals, recommended next action and agent-governance status.

Working with tasks

• Start assigns the task to you and marks it in progress.
• Tomorrow snoozes it for 24 hours.
• Complete records that your team handled the work.
• Dismiss requires a reason and keeps the decision in the audit history.
• Reopen returns completed or dismissed work to the active queue.

Tasks are never permanently deleted from this screen.

Does Pivra act automatically?

Not in this release. Generated tasks are marked Recommendation or Approval required. Pivra does not send customer messages, change provider credentials, make bookings or create commercial commitments from the Revenue Inbox.

The task model is ready for future Pivra AI employees. Agent work will use the same task identity, risk level, approval policy, version checks and audit timeline as human work.

Follow-up draft pilot

Selected pilot workspaces can prepare an AI-assisted reply for new-lead, quote and scheduled-follow-up tasks. Pivra sends the business name, the lead's first name and a bounded window of recent conversation text to the configured AI provider. It does not include the lead's email address or phone number in the model request.

The reply is an editable draft. A team member must review factual claims, pricing, availability and commitments before approving it. Approval records the reviewed draft in the audit timeline; it does not send the message. Email, SMS and WhatsApp delivery are intentionally unavailable in this pilot.

Generation, edits, approval, rejection, discard and failures are recorded against the revenue task. If the task or draft changes while it is open, Pivra asks the reviewer to refresh instead of approving stale content.

How to prepare for future agents

Keep lead statuses, follow-up dates, customer service schedules and integration connections accurate. Those records become the agent's grounded work context.

Future autonomous modes will be explicitly enabled, bounded and pausable. Consequential actions will continue to require the configured approval policy.