bitHuman On-Device Avatar Deployment Handoff (Delivery)

bitHuman On-Device Avatar Deployment Handoff (Delivery)

1. 01

   Install the bitHuman SDK and confirm the API key before client hardware ships

   Pull the Python, Swift, or Kotlin package, load the API key issued from the dashboard, and render a sample photo on the exact device model the client will use. Record whether the target runs CPU inference or needs WebGPU or an NVIDIA GPU so the handoff notes state the real hardware floor.

2. 02

   Create the client avatar in the no-code dashboard and lock the model choice

   Upload the client-supplied photo, select Essence 2 for a photorealistic presenter or Expression 2 for cartoon animation, and name the avatar to the client account. Screenshot the finished avatar ID into the handoff packet so delivery and support reference the same asset.

3. 03

   Write the personality, voice, and script configuration into a versioned file

   Capture the FAQ script, tone instructions, and voice selection as a single config artifact stored with the client record. Any later edit goes through that file, not ad hoc dashboard changes, so a retainer client can be rolled back to a known state.

4. 04

   Bind the avatar to the client surface and verify offline behavior

   Embed the avatar in the client website, kiosk, or app through the SDK, then disconnect the network and confirm lip-sync and chat still respond on-device. This is the step that proves the privacy claim the client bought, since audio, video, and prompts never leave the hardware.

5. 05

   Set the session and credit ceiling against the plan the client is billed on

   Map expected concurrent sessions to the plan tier: Creator allows 3 cloud sessions and 1,800 credits a month, Pro allows 10 cloud sessions and 10,000 credits a month. Flag any client whose traffic pattern would breach the tier before the month closes.

6. 06

   Run the delivery-to-support handoff review with the conversation log baseline

   Walk support through the avatar ID, config file, hardware floor, and the first week of conversation logs. Support owns monthly log review from that point, and delivery exits the account once the baseline is signed off.