AI calls are a real sales workflow in CRAIM, not a separate experiment.
What AI calls support
- creating call tasks
- launching calls when the team is ready
- keeping call sessions tied to the right workstream
- saving transcripts, summaries, and analytics
- turning call outcomes into follow-up work
Product principle
AI calling should be treated as a dedicated execution surface inside the broader AI sales operating model.
That means:
- voice workflows need their own setup and review
- CRM ownership and approval rules still matter
- post-call actions should flow back into the general sales loop
Telephony setup
Teams may use different telephony providers depending on region, account ownership, and call flow. Keep provider setup clear before enabling AI calls broadly.
Why that is correct
Calling has different timing, consent, routing, and review requirements than text workflows. It should not be treated like normal message drafting.
Product guidance
Knowledge base articles for AI calls should explain:
- what a call task is
- how a session relates to a workstream
- how provider selection works
- where transcripts and analytics end up
- what still requires human review or policy approval
Operating rule
Treat AI calls as one execution mode of the AI sales system, not as a disconnected product.