Explain the handover
The page follows the service from entering a number and a goal, through the phone menu and waiting, to connecting the user with a person.
Unhold
Make an unfamiliar service easy to imagine before committing to its hardest infrastructure.
The problem
The concept is hard to explain in a feature list. Visitors need to understand where the AI takes over and when they rejoin the call.
My part
Solo concept, copy and landing-page work. The call shown in the demo is scripted.
What this shows
I can make an early idea concrete through product framing, copy and interaction design before building the full service.
Where it started
Unhold explored a service that would navigate a hotline menu, wait on hold and connect the user when a person answers. The work reached a Polish landing page and a scripted interaction demo.
See it in action
English AI narration · Subtitles included · Play with sound, or read the transcript.
Read the video transcript
0:00 I turned the frustration of waiting on hold into a clear, testable product concept.
0:07 This session is a scripted demonstration, showing the experience before a real calling system exists.
0:14 The page explains the problem using published research on time spent waiting.
0:20 The proposed flow is simple: the assistant waits, then hands the call to the person.
0:26 The concept also explores phone menus in languages the caller does not speak.
The decisions behind the product
Prototype the experience visibly
A scripted terminal demo shows menu choices, waiting and detecting a human answer. It illustrates the intended flow without placing a real call.
Explore the presentation
I made nineteen landing-page variants and assembled the selected page with sourced background research and an early-access section.
What came out of the work
A tangible product concept
The delivered page and scripted demo make the proposed service understandable enough to discuss and evaluate.
A deliberate prototype scope
This is an archived concept. A live calling backend and call handover were not built, and the case does not claim validated demand or time saved.
Search visibility
Google Search ConsoleGoogle search impressions
Domain property: ominkolejke.pl (all subdomains)
- Latest month
- 11 Sept - 30 Sept 2026
- First month
- 01 Apr - 30 Apr 2026
Appearances in Google results. No search clicks were reported in this chart period.
Source, methodology and monthly data
Open Google Search Console report · Checked 8 Oct 2026
Domain property: ominkolejke.pl (all subdomains). Provider timezone: America/Los_Angeles.
- Six complete calendar months: 1 April to 30 September 2026. Current is September; comparison baseline is April. Both comparison months have 30 days. This is not a comparison against the preceding six months.
- Final web-search data, all countries and devices, America/Los_Angeles reporting timezone. Search clicks are not website visits or unique visitors.
- Domain properties include all subdomains with property aggregation. Documentation pages retain exact page filters from the preceding evidence collection and measure documentation interest, not adoption.
- Monthly chart values and the six-month total are reconciled with independently queried totals.
- The percentage, where shown, compares September 2026 with April 2026, the last and first complete months of this window.
- April has fewer than 100 events, so absolute counts are shown without a percentage growth claim.
- No Google search clicks were reported in this six-month window; impressions show search visibility only.
- For fewer than 100 events in the baseline period, the comparison shows absolute counts instead of a percentage.
| Month | Google search impressions |
|---|---|
| 1 Apr - 30 Apr 2026 | 0 |
| 1 May - 31 May 2026 | 0 |
| 1 Jun - 30 Jun 2026 | 0 |
| 1 Jul - 31 Jul 2026 | 2 |
| 1 Aug - 31 Aug 2026 | 2 |
| 1 Sept - 30 Sept 2026 | 1 |
Inside the implementation
Explore the features, architecture and quality checks
What I built
- A Polish landing page in five sections: the hero, the cost of waiting, how it works, menus in other languages, and early access
- An animated terminal that replays a scripted mock call: the AI hears the menu, presses 2 for customer service, waits on hold and detects a person. No real call is placed
- Outside research on hold times and language support, with every figure credited to a named source
- 19 design variants of the page, explored before the final build
- Scroll-triggered reveals and staggered cards built with Framer Motion
How it works
- DescribeIn the concept, you enter the hotline number and say what you need.
- NavigateThe AI calls, picks the menu options and waits on hold for you.
- Hand overWhen a person answers, the AI connects you to the call.
Quality and reliability
- Prerendered at build time and served from the Vercel CDN cache
- Consent-gated analytics: cookieless Umami always, PostHog only after an explicit yes
- Strict TypeScript
Technology
Explore another problem I worked on
- MeshExplored phone-to-phone messaging without mobile internet through a one-day native networking prototype.
- Lifecycle TrackerDesigned a workspace that organizes product decisions, evidence and next steps around the stage each product has reached.
- Claude Limits MonitorPut Claude usage limits into a browser badge and the macOS menu bar, close to where I work.