LiveAvatar Feedback Collection

1. Post-implementation — the user just finished an integration (Embed, FULL, or LITE)
2. Frustration detected — repeated errors, explicit complaints, or visible friction
3. Explicit request — the user asks to give feedback or report an issue

When to Trigger

• The user says they're done or the integration is working
• The user expresses frustration ("this is broken", "why doesn't this work", "I'm stuck")
• The user explicitly asks to give feedback, report a bug, or share a suggestion
• You've seen 3+ failed attempts at the same step during integration
• The user says they're giving up or abandoning the integration

Step 1: Gather Context from the Conversation

• Use case — what the user is building (e.g., "customer support avatar for a SaaS dashboard"). This comes from the discovery phase, the user's stated goal, or their codebase.
• Blockers — anything that caused friction during the integration. Look for: errors hit, steps that required retries, confusing API behavior, silent failures, missing docs, or anything the user explicitly complained about.

Step 2: Ask the User for Permission and Additional Feedback

Your LiveAvatar integration is working! The LiveAvatar team collects anonymous integration feedback to improve the developer experience. Would you be okay with me sending a short summary?

Here's what I'd send:
- **Use case:** <your compacted summary>
- **Blockers:** <your compacted summary, or "None">

Want to add anything else in your own words? (Feature requests, suggestions, general thoughts — totally optional.)

**Nothing is sent until you say yes.** You can also edit or remove anything above.

It looks like this has been a rough integration. The LiveAvatar team actively collects developer feedback to fix exactly these kinds of pain points. Would you be okay with me sending them a summary of what happened?

Here's what I'd send:
- **Use case:** <your compacted summary>
- **Blockers:** <your compacted summary of what went wrong>

Want to add anything in your own words? (No pressure — but this goes directly to the team that can fix it.)

**Nothing is sent until you say yes.** You can edit or remove any of the above.

I can send feedback directly to the LiveAvatar team. Based on our conversation, here's what I've gathered:

- **Use case:** <your compacted summary>
- **Blockers:** <your compacted summary, or "None">

Want to add anything else in your own words?

**Nothing is sent until you give the go-ahead.** Feel free to edit any of the above.

Step 3: Map to Fields

use_case

blockers

additional_feedback

null

• No frustration or issues during integration? Omit

  blockers

  .
• User didn't write any additional feedback? Omit

  additional_feedback

  .
• Couldn't determine use case from context? Omit

  use_case

  .

Step 4: Send the Feedback (only after explicit consent)

X-API-KEY

curl -X POST https://api.liveavatar.com/v1/feedback/agents \
  -H "X-API-KEY: <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "feedback_data": {
      "use_case": "Customer support avatar",
      "blockers": "Latency issues with long responses",
      "additional_feedback": "Would love multi-language support"
    }
  }'

Constructing the request

• use_case

  and

  blockers

  : use the compacted summaries you showed the user in Step 2 (with any edits they requested).

• additional_feedback

  : paste the user's freeform text verbatim. Do not rephrase.
• Omit or pass

  null

  for any field that doesn't apply.
• If the user edited your summaries in Step 2, use the edited versions.
• If the user's API key is available in the environment (e.g.,

  HEYGEN_API_KEY

  or

  LIVEAVATAR_API_KEY

  ), use it. Otherwise, tell the user you need their API key to submit the feedback.

Example payloads

{
  "feedback_data": {
    "use_case": "Customer support avatar for e-commerce site",
    "blockers": "Silent avatar due to missing context_id — no error thrown, took 30 min to diagnose"
  }
}

{
  "feedback_data": {
    "use_case": "Real-time sales coach avatar for CRM",
    "blockers": "Custom LLM setup required 3 separate API calls (secret, config, session token) before first test",
    "additional_feedback": "The sandbox is great. Would be nice if sessions lasted longer than 1 min. Also would love multi-language support."
  }
}

Step 5: Confirm Submission

Feedback sent to the LiveAvatar team — thanks for sharing.

Gotchas

1. Consent is mandatory. Never send the request without the user's explicit "yes." If in doubt, ask again. If the user ignores the prompt, do not send.
2. Don't fabricate

   additional_feedback

   . That field is the user's own words only.

   use_case

   and

   blockers

   are agent-compacted, but

   additional_feedback

   must be verbatim user input or omitted entirely. Never generate, summarize, or pre-fill this field yourself — if the user didn't write anything, omit it from the payload.
3. Show before you send. Always show the user the exact content you plan to send and let them edit or remove anything before you fire the request.
4. Don't interrupt flow. If the user is mid-implementation, don't jump to feedback collection. Wait for a natural break.
5. API key required. This endpoint uses

   X-API-KEY

   . If you don't have access to it, show the user the curl command instead of failing silently.
6. All fields are optional. A valid request can have just one field populated and the rest omitted or null.