What to do when a design partner for AI voice agents never uses it

When a partner stops using the product, diagnose access, workflow fit, reliability, incentives, and competing priorities separately. Silence is not proof that the idea is bad or that the partner is careless. Ask about the last attempted use and the specific point where work stopped.

Start with the decision

Review permissioned usage and support records with the participant. Test whether the team can complete the intended task under current conditions. Agree a short recovery experiment or an explicit end rather than leaving the engagement indefinitely active.

The illustrative scenario

This is an educational workbook. The company or fund and all numerical inputs below are fictional. They are not ADIN results, customer claims, market benchmarks, or a forecast.

The fictional product handles appointment requests for a multi-location service business. A caller may change their request mid-conversation, and the scheduling system is the final record of an available slot.

A short call is not useful if it books the wrong appointment. Separate successful scheduling from hangups, transfers, and calls where the caller never confirmed the details.

Turn the scenario into an evidence decision

Consider a review of AI voice agents in which a confident explanation arrives before the supporting records. Start with the first question in the table. Write down what an answer would change: the next interview, the experiment's scope, a request for specialist review, or a decision to wait. A question without a consequence can produce a longer document while adding little understanding.

Next, inspect the record named in the table and record its date, owner, permission boundary, and limitations. Collect permissioned test calls, interruption cases, confirmation records, and failed booking attempts. Keep different languages and noisy environments visible in the sample. If the record contradicts the explanation, preserve both accounts and ask which definition, period, or workflow differs. Do not silently select the version that makes the opportunity look strongest.

Finish with a conditional statement: if the specified evidence supports the claim under these conditions, take the named next step; otherwise investigate the unresolved question. A stalled partnership becomes informative when it identifies a testable cause. If neither side can name a learning objective or accountable owner, continuing may add little evidence despite preserving a promising logo. This worked exercise is about the decision process. It does not assert that a fictional company has met a real diligence standard or that a template can authorize an investment.

Use this worksheet

Answer the questions with a source, date, owner, and next action. Mark an unknown as unknown. Use public or permissioned information and involve a qualified specialist when a question requires expertise beyond the team’s competence.

1. Could the user access the product?
2. Was the task still needed?
3. Where did the attempt stop?
4. Who owns the next action?
5. What date triggers a stop decision?

Questions specific to this scenario

• Who confirms the booking?
• What happens when a caller interrupts?
• How is a failed transfer recovered?

Collect permissioned test calls, interruption cases, confirmation records, and failed booking attempts. Keep different languages and noisy environments visible in the sample.

A concrete next test

Run permissioned tests with an interruption, an unavailable appointment, and a failed transfer. Ask the scheduling owner to verify the final records, then inspect what the caller was told. A correct transcript alone does not establish a correct booking.

Interpret the result

A stalled partnership becomes informative when it identifies a testable cause. If neither side can name a learning objective or accountable owner, continuing may add little evidence despite preserving a promising logo.

Compare completed, correct bookings with the existing phone process. Include repeat calls and staff repair time instead of measuring call duration alone.

Sources and method

These primary resources provide background for the concepts. The fictional scenario, calculations, and worksheet are ADIN educational examples; the sources do not report or validate those invented results. Reviewed October 11, 2026.

• First Round Review: Sierra’s design partner strategy
• NIST: AI Risk Management Framework