dusk bot
use casescrm updates

dusk botuse cases

turn sales notes into crm updates you can verify

a buyer can move the demo without moving the close date. give a bot the call note and the hubspot deal id.

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

have it compare the note with the current fields, then return just the changes you can back up. the rep who owns the forecast decides what goes into the record.

pixel art: a blue pixel bot, a mint pixel bot and an indigo pixel bot beside a briefcase and a notebook, on a lilac hill in front of little green islands on a lake, one saying "which field changed?"

the routine

pair every call note with its deal id. add the pair to the call log after a call.

paste this into a chat with your bot

every weekday at 5 pm, review today's deal ids and dated call notes in sales-call-log.md in your project folder. for each pair, get the current hubspot deal. compare the next step, close date and amount with the buyer's words. show a proposed change only where the note supports that exact field. include deal id, field, old value, proposed value and evidence.

put tentative language under 'ask the rep'. skip deals without a matching id. leave every field alone. if no pairs came in today, stay quiet.
when
weekdays at 5 pm after reps add their notes
needs
hubspot read only, a deal id and a dated note for each call. use your call log’s filename and give the bot access to its folder.

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

example proposal
deal 804 | next step | send samples → book a fitting | bernadette asked for a fitting after the samples arrived.
close date | keep current value | tuesday refers to the fitting.
amount | no proposal | buyer asked for a quote on a larger order.

start with the right opportunity

match on deal id before reading fields. one customer can have a renewal and a new order open. a company name won't tell you which pipeline entry the buyer meant. get the id from the deal the rep had open during the call.

compare what the rep heard with what is on file

ask for the smallest edit the evidence supports.

  1. use hubspot to read the named deal and its current properties.1
  2. extract what changed from the call note. preserve dates and currencies as written.
  3. show the old and proposed values on one line. if the current value already says the same thing, omit the edit.

let the forecast owner apply the edit

reopen the deal before changing the forecast. a colleague may have updated it since the bot read it. if the old value in chat differs from the live value, stop and ask the rep which is current.

use a regular field mapping for a fixed transfer between systems. dusk bot earns its place when someone's words need interpretation.

the guard rails

  • keep hubspot read only for the comparison. the rep enters accepted edits in the live deal.
  • leave stage and probability to the deal owner. enthusiasm alone gives you no basis for a forecast.
  • strip personal details from call notes before pasting them. include only the evidence for the proposed fields.

try it in 2 minutes

  1. copy one deal id and its call note
  2. ask for a proposal on the next-step field
  3. compare the old value with hubspot before entering the edit

what it could save you

around 12 minutes for a batch like this

6 call notes × 4 minutes reconciling each = 24 minutes
6 proposals × 2 minutes reviewing and entering each = 12 minutes
24 - 12 = 12 minutes

a rough estimate. it assumes:

  • time both approaches on six deals
  • include collecting ids and correcting any proposals
  • exclude call note writing only if you already do it

what it looks like

an invented call about a uniform order

before

the next step still says “send samples”. bernadette confirms delivery and asks for a tuesday fitting. the rep also mentions a possible second order.

after the bot

the rep updates the next step and books the fitting separately. the forecast keeps its amount and close date until the buyer confirms an order.

an illustration with made-up names and numbers.

mistakes people make

overwriting an amount with a range

keep the range in the evidence. ask which value your forecasting rules accept.

treating a blank as an instruction to clear a field

absence of a new value means leave the existing value alone.

questions

can the bot change a hubspot deal itself?

hubspot has an update action.1 keep this routine read only. for a separate editing routine, limit the allowed actions and write “ask me before you change anything” into the message.

what if several calls mention the same deal?

sort the notes by call date and look for a buyer correction. ask the rep about conflicts before entering either value.

sources

  1. composio: hubspot actions, checked 12 november 2026
  2. dusk bot docs: files and connected apps
  3. dusk bot docs: routines

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].