# Chatbot

By Munawar Khel / Day One Technologies / 2017–22 / 2 min read

Published at https://munawarkhel.com/work/day1-technologies/chatbot/

Pitch, not delivered.

A conversational assistant for **Cloud Employee**, a B2B service business, designed to do the work a sales and support team would otherwise do by hand.

- Company: Day One Technologies
- Timeline: November 2017 – April 2022
- Platform: Mobile, in-product chat interface
- Category: B2B services, conversational commerce, lead generation and customer support
- Status: Pitch, not delivered

## The proposition

A conversational assistant for **Cloud Employee**, a B2B service business, designed to do the work a sales and support team would otherwise do by hand. Rather than a single generic bot, the pitch is built as **five purpose-made conversation flows**, so the bot qualifies a visitor and routes them: answering general questions, explaining the engagement models, capturing a quote request, booking a call, or sending resources.

The quote flow is the most developed and shows the commercial intent clearly. The bot asks the visitor for their website, probes how they want to engage, and then hands off to a human partner, so the conversation is a qualification funnel rather than a help widget.

## Design direction

Deep blue throughout, with a rich gradient on every screen and a soft flowing wave graphic behind the conversation to stop a long thread feeling flat. The bot has a distinct circular avatar mark so machine and human turns are never confused. User replies sit in solid accent bubbles on the right, bot replies in translucent panels on the left, and **quick-reply chips** carry most of the interaction so the visitor can move without typing. A persistent "write a reply" input with attachment controls keeps free text available.

## What was designed

- **General information flow**, opening with a greeting and an offer to help with hours, products, or pricing, then branching on whether the visitor is an existing customer and which team they want (sales or support)
- **FAQ flow**, answering "what models do you offer" with a selectable list of engagement models, each expandable for detail
- **Request a quote flow**, the longest sequence: capturing the request, collecting the visitor's website URL, asking how they intend to engage, and closing with a handoff to a human partner
- **Schedule a call flow**, booking a conversation directly in the thread
- **Request resources flow**, delivering materials on request
- Shared conversation components: bot avatar, quick-reply chips, link and URL handling in-thread, expandable list items, and the reply composer

## What it demonstrates

The only **pure conversational-interface** work in the pitch set. It shows chat as a structured product surface rather than a support afterthought: branching flows, quick-reply-led interaction that minimises typing, and a designed handoff point from automation to a human. Useful evidence for conversational UX and lead-qualification design.