dusk bot
use casesclient onboarding

dusk botuse cases

prepare a client onboarding brief before kickoff

catch the extra deliverable before it lands on the kickoff agenda as a promise. a bot can compare a client's intake answers with the agreed scope in google docs.

by the dusk bot team · checked · how we made this

have it prepare a brief that distinguishes what the client bought, what they want and what someone still needs to decide.

pixel art: a blue pixel bot and a mint pixel bot beside a briefcase and a folded map, on a grassy meadow in front of sand dunes by the sea, one saying "what blocks kickoff?"

the routine

pair the intake response with the agreed scope yourself. give the bot both references for the same engagement.

paste this into a chat with your bot

on weekdays at 3 pm, read the google sheet “kickoff register”. for each row marked ready today, use its typeform response reference and agreed google doc link. compare requested deliverables, dates, approval contacts and assets. for each item show what the scope says and what the client answered.

put requests outside the agreement under 'discuss scope'. turn missing inputs into questions for kickoff. separate facts from proposed next steps. if the client or project details disagree, stop before combining anything. keep the brief in this chat. don't contact the client, invite anyone or grant access.
when
weekdays at 3 pm for the engagement pairs you named
needs
read only typeform, google docs and google sheets connections, a response reference and the agreed scope doc. replace the kickoff sheet name with yours.

what comes back looks like this (an example, not a real inbox)

example kickoff brief for darlene
agreed | a printed drinks menu, one size. client also wants a window poster.
discuss scope | is the poster a separate quote?
ready | menu copy received in intake.
blocked | no print dimensions. ask who has the printer's final spec.

start with what the client already told you

avoid making the client answer the same question twice. read the intake alongside the agreement. accept a clear answer and record where it came from. when the form asks for a launch date, keep the client's hoped-for date separate from the delivery date you agreed.

assemble a brief for one engagement

tie both sources to the same piece of work.

  1. find the completed response on the named typeform and match its reference.1
  2. read the agreed scope doc by id in google docs.2 confirm its project name before comparing.
  3. group the findings by what can start, what is missing and what needs a commercial decision. put the exact question beside each gap.

let the account owner set expectations

ask the question before promising to do the work. a wish in an intake form doesn't change the agreement. the account owner settles scope, dates and who can approve a proof. bring the brief to kickoff and write down those decisions there.

if you need signed acceptance or a client portal, use your existing contract or onboarding system for that part.

the guard rails

  • keep the apps read only. changes to the agreement belong with the account owner.
  • use a separate brief for each engagement. leave access credentials out of both the form and the brief.
  • a connected-app send asks first by default, including a client invitation.5

try it in 2 minutes

  1. pick one completed intake and its scope doc
  2. ask for one confirmed deliverable and one question
  3. open both sources beside the brief and trace the answer

what it could save you

around 9 minutes per kickoff if these times match yours

16 minutes comparing intake and scope by hand
- 7 minutes pairing sources and correcting the brief
= 9 minutes per kickoff

a rough estimate. it assumes:

  • time briefs of similar size and complexity
  • include opening the agreed version and resolving a bad source match
  • exclude the kickoff call itself from both timings

what it looks like

an invented menu design kickoff

before

darlene asks for a menu and a matching poster in the intake form. the agreed scope covers the menu. neither source gives final dimensions.

after the bot

the designer can start on the menu copy. the owner brings a poster pricing question to kickoff and asks for the printer's dimensions before laying out the page.

an illustration with made-up names and numbers.

mistakes people make

treating the person who filled out the form as the approver

ask who can sign off. an assistant can complete intake on someone else's behalf.

reusing the last contract from the same client

name the doc for this engagement. recurring clients can have several agreements in force.

questions

what if the client just submitted the form?

recent typeform responses can take up to 30 minutes to appear through the connector.1 ask again later before asking the client to repeat intake.

does a missing asset have to block the whole kickoff?

tie the missing asset to the work that depends on it. the team might be able to review copy while it waits for a print-ready logo.

sources

  1. composio: typeform actions, checked 20 november 2026
  2. composio: google docs actions, checked 20 november 2026
  3. dusk bot docs: files and connected apps
  4. dusk bot docs: routines
  5. dusk bot docs: a bot’s computer

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].