Give the Trial One Real Job
This playbook is designed to produce an answer—not a tour. By the end of day three, you should know whether ArcTactic can coordinate a repeatable workflow with the quality, visibility, and control your business needs.
Before You Start
Choose a workflow that is frequent, bounded, and easy to inspect. Good trial workflows have a clear input, a clear finish line, and a human owner who can judge the result.
- Good: qualify new enquiries and create the correct CRM follow-up task.
- Good: draft answers for routine support questions using an approved knowledge source.
- Good: prepare follow-up messages for leads that have not replied.
- Avoid: “automate the whole business” or workflows that require unapproved access to sensitive systems.
Keep a human approval step
During the trial, require approval before external messages, calls, contracts, or billing actions are sent. Expand autonomy only after reviewing representative outputs.
Day 1: Connect the Minimum Context
Set up only what the chosen workflow needs. Extra integrations add noise and make failures harder to diagnose.
- Create the workspace and enable MFA for the account owner.
- Connect the relevant inbox, calendar, CRM pipeline, or messaging channel.
- Upload current FAQs, service descriptions, pricing, and operating instructions used by the workflow.
- Define the pipeline stage, task, or document that marks successful completion.
- Record three representative examples to use on day two.
Day-one exit check
The AI team can read the required source, identify where finished work belongs, and cannot access unrelated data.
Day 2: Launch With Guardrails
Run the representative examples before introducing live work. Review the task route, source material used, proposed action, and any handoff between AI specialists.
- Confirm names, prices, policies, and dates are drawn from approved sources.
- Check that uncertain cases are escalated rather than guessed.
- Review tone and formatting for customer-facing drafts.
- Verify that CRM records, tasks, and pipeline stages are updated in the intended location.
- Keep outbound actions in approval mode until the samples meet your standard.
Once the examples pass, introduce a small batch of live work and monitor the activity log.
Day 3: Review the Work
Evaluate the workflow against a short scorecard. The point is not whether every edge case is solved; it is whether the core process is useful, controllable, and worth refining.
- List corrections that require better source material rather than a different workflow.
- Identify steps that should remain human-owned.
- Decide whether to continue, revise the workflow, or cancel before the trial ends.
Trial and Billing Terms
Payment details are required to start the trial. Your selected subscription begins automatically when the three-day period ends unless you cancel beforehand.
- Monthly: $497 USD per month.
- Annual: $4,970 USD per year.
- Usage: voice calling and messaging may create separate usage charges when enabled.
- Payments: Paddle is the Merchant of Record and displays applicable taxes at checkout.
Review the Terms of Service and Refund Policy before starting.
If the Workflow Stalls
- Pause live actions and keep drafts in approval mode.
- Confirm the integration is connected and the required permission has not expired.
- Check whether the source document contains the missing answer or instruction.
- Capture the workflow name, failed step, timestamp, and visible error.
- Submit those details through the support portal.