How Konfyre Voice
tracks a workflow.

One task, several call attempts.

A workflow is the customer task you want to complete. Each call or callback is a separate attempt to move it forward. The workflow can stay open after a call ends.

Label captured and verified values.

An answer can have the right format and still need verification. Record whether the caller supplied it, a format check passed or an approved source confirmed it.

• Captured: the caller supplied the value.
• Format checked: it matches the required type or format.
• Source verified: an approved source confirmed it.
• Needs review: a person or approved source still needs to check it.

Update the route when an answer changes.

In this example, changing team size from 12 to 120 sends the request for larger-team review. Keep the previous value and rule version in the record, and stop using the earlier scheduling route.

{
  "example": true,
  "field": "team_size",
  "previous": 12,
  "current": 120,
  "rule": "larger_team_review_v4",
  "next_step": "human_review"
}

Conceptual example, not an API request or a published endpoint contract.

Confirm actions with a system receipt.

Track the action result separately from the agent’s words. Mark it confirmed only when the source system returns the required receipt.

• Requested: the workflow asked for the action.
• Pending / unknown: confirmation is not yet available.
• Confirmed: the source system returned the required receipt.
• Failed: recovery or human follow-up is required.

Measure calls and completed work separately.

Track call attempts, missing information, action status and workflow outcomes separately. When reporting completion, include open workflows in the denominator and record the reporting cutoff.

Agree the scope, then test it.

1. Define the task, required fields and approved knowledge.
2. Confirm language, country and provider support.
3. Map permitted actions and human review points.
4. Test missing data, corrections, callbacks and action failure.
5. Review access, recordings, transcripts and retention.
6. Check a completed workflow against its source-system evidence.