Plan your first workflow

Start with a recurring task that your team understands well. A useful first workflow has a named owner, accessible inputs, a recognizable finish, and a manageable set of exceptions.

Choose a bounded outcome#

Describe what should exist when the work is done. “Improve customer operations” is too broad to evaluate. “Prepare a renewal review with open commitments, missing information, and recommended next steps” gives reviewers something concrete to accept or return.

Choose a starting scope that can be evaluated using representative examples. Identify what remains outside the agent's responsibility, such as negotiating terms or committing to a customer deadline.

Map the work as it happens today#

Walk through a real case with the people who do the work. Capture where it begins, which systems they consult, how they decide what to trust, and what they hand over. Include the inconvenient cases: conflicting records, missing documents, unavailable approvers, and failed updates.

For each step, identify the system owner and whether the agent needs to read information, prepare a draft, or change a record. These require different permissions.

Write a workflow brief#

Use this outline to prepare a discussion with your Coryntas team:

Outcome: the deliverable or resulting business state.
Inputs: the records, documents, and time period in scope.
Start condition: the request or event that should begin work, subject to supported integration.
Allowed actions: what may be read, drafted, or changed.
Review points: the decisions that require a named person.
Exceptions: when to stop, ask for clarification, or hand over.
Acceptance: the evidence needed to consider the work complete.

For example, a renewal brief can permit reading approved account records and drafting an internal summary while requiring review before any customer communication.

Agree on acceptance#

Select normal cases and exceptions with expected outcomes. A good evaluation checks the sources, permitted actions, and final result together. Include cases where the correct behavior is to decline an action or request more context.

Take the agreed brief into deployment preparation. Use the Agent Library for inspiration, then adapt the scope to your own systems and responsibilities.