CRM with Ticketing

Features

Industries

Reference

More

Start now
  1. CRM with Ticketing
  2. Your team's assistant
Reference

Put an AI agent to work in CRM with Ticketing

Use Proto to prepare customer-support reviews while people retain responsibility for decisions and evidence.

Set it up

  1. Teach your agent ERP.AI

    Load the ERP.AI skill and paste the output into your agent. It explains how to read and update records in your workspace.

    curl -fsSL https://www.erp.ai/skill.md

  2. Give it a role

    Assign the agent its own user and one of the 5 roles. It gets exactly the access that role has, and no more.

  3. Check what it can reach

    Confirm which records, actions and connections the agent can use in your workspace before you point it at real data.

  4. Review its work and usage

    Check the drafts and changes it proposes, and watch its usage receipts as you give it more to do. Agent work uses prepaid credits.

What the agent can do

  • Service Agent: Find assigned tickets, gather the customer context and help prepare a clear response or support-link submission.
  • Service Supervisor: Bring the submitted revision and supporting evidence into view before an independent decision, or compare a pending receipt with its linked effects.
  • Auditor: Trace the permitted event, decision and receipt history for the selected ticket without changing the operating result.
  • App Administrator: Check customer and team-member records for the intended organizational context.

What stays with a person

  • The assistant cannot turn an internal note into evidence of a real customer response or accept an account-support request without the designated review.
  • It must respect organizational scope and visibility.
  • Reconciliation cannot repeat an external action simply to discover whether it already succeeded, and external channel actions require their own authorization.
  • Assistant requests, imports and connected operations follow the platform's usage billing.

The assistant cannot turn an internal note into evidence of a real customer response or accept an account-support request without the designated review. It must respect organizational scope and visibility. Reconciliation cannot repeat an external action simply to discover whether it already succeeded, and external channel actions require their own authorization.

Assistant requests, imports and connected operations follow the platform's usage billing. Review the [pricing details](/crm-with-ticketing/pricing) against the pilot's expected activity before expanding access.

Set up CRM with Ticketing your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started