Reception · Phone reception across industries
Show calls that several industries might miss, then let one assistant handle those needs. Create the response gap in the first half and demonstrate the solution through dialogue in the second.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Introducing Reception, an AI receptionist platform for small businesses, built on ElevenAgents.
Every missed call coul · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f6f0}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Motion and composition
Local motion · Composition rules
Differentiate scenes with objects, unify the problem through calls
Use a phone and a few industry objects to establish appointments, on-site work, and everyday affairs. Give every scene a clear incoming-call state as the heading gradually forms the shared problem of nobody answering.
Support objects with white or pale space and use the phone screen as a dark anchor. Set sentences in regular sans serif with slightly bolder keywords; avoid a different effect for every word.
Focus the turning point on one assistant figure
After the transition sentence, introduce a warm orb or an equally simple assistant symbol. Condense scattered objects into a central subject so subsequent dialogue is easier to follow.
Alternate questions and answers, making results concrete and readable
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Introducing Reception, an AI receptionist platform for small businesses, built on ElevenAgents.
Every missed call coul · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f6f0}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="16" data-end="28"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Have the caller state a need first, the assistant ask or respond next, then provide a booking, record, or handled result. Keep speaking direction, avatar, or color consistent; gently recede the previous message while keeping the new one clear.
Which services suit this structure
Choose scenarios with real response gaps, such as appointments, after-sales support, or reception. Replace industry objects, problems, and final results, preserving the convergence from multiple calls to one service entry; closing feature cards should summarize only demonstrated capabilities.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Adapt to service-response stories, preserving multiple needs→response gap→delegation→result
- Replace industry, problem, and dialogue while keeping speaker identities clear
Production constraints
Scene objects / telephone / incoming-call label / problem text / assistant orb / conversation card / feature group
- Use calls from multiple industries to establish the same problem in the opening, then present a single glowing sphere as the solution in the middle
- Alternate question and answer cards to show caller and assistant responses rather than a simultaneous static stack
- Return to the problem at the end and show an action entry point