How to sell AI Sticker Pack
Who is this for
Section titled “Who is this for”Sales people and agency partners who present the product to event organisers. No technical knowledge needed.
- One sentence: every guest leaves the event with a Telegram sticker pack of their own face, made from one photo at a tablet station.
- Three arguments: the event stays in chats afterwards; guests need no app; nobody stands in a line waiting.
- Promise only what is on the “can promise” list below. It is the same list the landing page is tested against.
- Never promise prices in public, exact likeness, working without internet, branded outfits, printing, or delivery outside Telegram.
- Every request goes through the form on the landing page (
pack.eventtalks.uz) and becomes a card in the sales group.
Who buys it
Section titled “Who buys it”| Buyer | What they want | Lead with |
|---|---|---|
| Event agencies | A fresh activation they can add to a client’s programme without running it themselves | “End to end: we set it up, rehearse and monitor it” |
| Corporate event teams (forums, conferences, company parties) | Guests talking about the event afterwards | “Stickers keep getting sent after the venue empties” |
| Brand and marketing teams (launches, stands at exhibitions) | Traffic to the stand and a branded touchpoint | “A station in your colours and logos; a line that moves” |
The product was piloted through an event agency for a forum of about 70 guests with one station.
The pitch
Section titled “The pitch”The landing page’s own structure is the pitch. Use its order.
- Show the result first. Open the showcase on the landing page: real packs of 12 stickers for six different demo people and six outfits. People buy what they see.
- Explain the guest’s minute. Start on the tablet → scan the QR code → agree in Telegram → pick an outfit → photo. A couple of minutes later the pack arrives in Telegram.
- Give the three reasons.
- Photos sit in a camera roll. Stickers get sent. The event stays in conversations.
- No app. A QR code and the Telegram the guest already has.
- No queue. The station is free right after the photo; the pack arrives later.
- Take the work off their plate. They do not look for a contractor, install anything for guests, collect consent on paper, store or delete photos, or keep guests waiting.
- Answer privacy before they ask. Consent first; photos deleted automatically within 72 hours; the database keeps only service data kept.
- Close with the process. We talk through venue and guest flow, set up, rehearse on site, and stay on watch during the event.
What we promise
Section titled “What we promise”These statements are true of the product as built. Each links to the page that proves it.
| Promise | Proof |
|---|---|
| A QR code and Telegram — no app to install | Guest session flow |
| The guest’s consent is taken before any photo | ADR-004 |
| The guest picks an outfit on the tablet | Kiosk components |
| 12 chunky cartoon stickers with the guest’s face | Generation pipeline |
| The pack arrives in Telegram in a couple of minutes | Capacity — measured about 1–1.3 minutes on a quiet queue |
| The station does not wait for generation and is free at once | ADR-003 |
| One pack per Telegram account | ADR-006 |
| Photos are deleted automatically within 72 hours; the database never contains a photo, only service data (Telegram account, time, status, pack link) | ADR-005. Do not say “nothing is kept”: service data, server logs and database backups are kept longer than 72 hours — see Known gaps, L9–L11. |
| Monitoring and technical support during the event | Monitoring & alerts |
| The station in the colours and with the logos of the event | Venue requirements and branding |
| Set-up for the event, with a rehearsal | Event playbook |
What we do not promise or mention
Section titled “What we do not promise or mention”| Do not say | Why |
|---|---|
| Prices, in any public material | Each event is priced individually. The public answer is “leave a request and we will tell you”. |
| Any number other than “12 stickers”, “a couple of minutes” and “72 hours” in public material | Other figures are either unmeasured or change with the venue and the load. Planning figures such as guests per hour per station, or backup retention of 14 days, may be given in a one-to-one conversation when asked, labelled as estimates — never on the landing page, in decks or in ads. |
| “Looks 100 % like you” or any likeness guarantee | The result is a stylisation that carries the guest’s features, not a photo. |
| “Works without internet” | The tablet, the server, Telegram and the AI service all need a connection. |
| WhatsApp, e-mail or any delivery other than Telegram | A sticker pack lives in Telegram. |
| Printed stickers | The product does not print. |
| Branded outfits, props or branded stickers | Only the station screen is branded. Outfits come from our catalogue, and stickers carry no logos or text. |
| Names of AI models or vendors | They can change without notice and are not a selling point. |
| A backup AI provider, “fallback” (not to be confused with the fallback request message in the sales group — see the glossary) | It is designed for but not live — see Known gaps. Offer “monitoring and support during the event” instead. |
| Client names, logos, testimonials, counts of past events | Nothing may be invented, and past clients have not agreed to be named. |
| The internal name of the art style | Describe it in words: “chunky cartoon”. |
| Words like “revolution”, “next level”, “all-in-one”, “AI magic” | Tone rule of the landing page. |
The landing page’s automated tests enforce most of this list on its texts; apply the same list to presentations and messages.
Honest limits to mention when asked
Section titled “Honest limits to mention when asked”- A guest without Telegram cannot get a pack.
- The interface of the bot and the station is in Russian today. Other languages need preparation before the event.
- Very bright or uneven light at the stand makes skin tones less accurate.
- A second pack for the same guest is possible only through the operator.
- For events beyond a few hundred guests we need advance notice to prepare capacity — see Scaling scenarios. Do not confirm a large event before an engineer has read that page.
What to collect from the client
Section titled “What to collect from the client”The form asks for the minimum on purpose. On the first call, find out:
| Question | Why we need it |
|---|---|
| Date, city, venue | Schedule, internet and power at the site |
| Expected number of guests and event duration | Number of stations, budget, provider quota |
| When guests arrive in waves (registration, breaks) | Peak load on the station |
| Audience language | Bot and station texts |
| Brand materials: colours, logos, fonts | Station screen branding |
| Who is the organiser’s contact on the day | Incidents and decisions |
| Any rules of the client’s legal team about photos and personal data | The consent text and retention |
Where to go next
Section titled “Where to go next”- Venue requirements and branding.
- Client FAQ — ready answers.
- How a request is handled.
Last verified: 2026-11-13 against ai-sticker-pack@b715418 and ai-stickers-landing@e350ff5.