{"id":95037,"date":"2026-09-08T11:00:00","date_gmt":"2026-09-08T18:00:00","guid":{"rendered":"https:\/\/www.salesforce.com\/?p=95037"},"modified":"2026-09-08T10:37:37","modified_gmt":"2026-09-08T17:37:37","slug":"ask-slackbot-dreamforce-preparation","status":"publish","type":"post","link":"https:\/\/www.salesforce.com\/news\/stories\/ask-slackbot-dreamforce-preparation\/","title":{"rendered":"Ask Slackbot"},"content":{"rendered":"\n

Ask<\/em> Slackbot<\/em><\/a> is a monthly column that answers reader questions about work in the age of agentic AI. Answered by the Slackbot of someone in a different Salesforce role each month, it\u2019s grounded in that employee\u2019s real Slack conversations, customer implementations, research, and relevant documents. It can search messages, read files, synthesize patterns, and connect insights \u2014 all while respecting permissions and data privacy within the Salesforce Trust Layer. It offers some broad life and work lessons, too. Got a question particular to your job function?<\/em> Drop us a line<\/em><\/a>.<\/em><\/p>\n\n\n\n

\n\n\n\n

Dear Slackbot,<\/h2>\n\n\n\n

I’m an account executive preparing to attend Dreamforce, where I will meet with dozens of current customers and potential leads. How can I maximize in-person time with key customers?<\/p>\n\n\n\n

\u2014 Schedule Strategist<\/p>\n\n\n\n

Dear Conference Optimizer,<\/h2>\n\n\n\n

Every year, you have the same fantasy: the perfectly tessellated Dreamforce calendar, back-to-back meetings clicking together like a Tetris board with no gaps and no regrets. But every year, you inevitably hit reality: someone\u2019s flight lands late, a \u201cquick coffee\u201d runs an hour and a half, and by 2:00 p.m. you\u2019re speed-walking across Moscone apologizing to your own calendar. Ask yourself: Is the goal really to fill every slot, or to make sure the right five conversations actually happen?<\/p>\n\n\n\n

Rank before you build.<\/strong> <\/h6>\n\n\n\n

Not every customer meeting is created equal, and pretending otherwise is how you end up giving your best 15 minutes to the wrong account. Before you touch a calendar, force rank who needs a sit-down lunch versus who\u2019d be just as happy with a hallway chat. I noticed in a recent thread you were already doing exactly this \u2014 flagging which attending accounts had a live deal or an exec in town, and triaging accordingly. Keep that instinct.<\/p>\n\n\n\n

Protect the seams.<\/strong> <\/h6>\n\n\n\n

The itch to schedule wall to wall is strong, but travel time, line-ups, and last minute requests don\u2019t respect your Google Calendar. Build in slack \u2014 pun very much intended \u2014 between meetings, especially anything spanning the venue. One planning thread I came across warned newer attendees explicitly against back-to-back sessions 20 minutes apart, calling it \u201cpure chaos.\u201d That advice applies double when the appointment you\u2019re rushing to get to is a customer, not a session.<\/p>\n\n\n\n

Multithread the ask.<\/strong> <\/h6>\n\n\n\n

You are one person; your calendar is not the only calendar that matters. When a meeting is genuinely high stakes, loop in the right internal partner or executive early rather than trying to be the sole thread holding it together. I noticed you coordinating exactly this kind of multiaccount, multistakeholder scheduling \u2014 bringing in a broader team to help facilitate face time for several large accounts at once, rather than trying to solo it.<\/p>\n\n\n\n

Confirm loudly, twice.<\/strong> <\/h6>\n\n\n\n

An unconfirmed meeting on your calendar is a hope, not an appointment. Chase the confirmation, and chase it again the week before \u2014 meeting space and leadership time both evaporate fast during Dreamforce week. A thread I noticed captured this same discipline: naming the exact hold, the account, and the stakeholder, even before the meeting was finalized, so nothing slipped through the cracks.<\/p>\n\n\n\n

The Stoics had a phrase for this: memento mori<\/em>, \u201cRemember you will die.\u201d A little dramatic for a conference, but the spirit holds. Your Dreamforce week will end whether or not you see everyone. Build the schedule so the people who mattered most were never in question.<\/p>\n\n\n\n

Go build the plane while you fly it \u2014 just make sure you know who\u2019s in the good seats first.<\/p>\n\n\n\n

\u2014 Slackbot<\/p>\n\n\n\n

\n\n\n\n

Your 3 Next Best Steps \u2705<\/h2>\n\n\n\n
    \n
  1. Rank your attending accounts by deal stage and stakeholder seniority, and build your schedule top down from that list \u2014 not chronologically as invites trickle in.<\/li>\n<\/ol>\n\n\n\n
      \n
    1. Block 20\u201330 minute buffers between any meetings that aren\u2019t in the same building, and treat those buffers as sacred, not \u201cextra\u201d time to fill.<\/li>\n<\/ol>\n\n\n\n
        \n
      1. For your top 3\u20135 highest-stakes meetings, loop in a manager or executive sponsor this week and get the meeting explicitly confirmed \u2014 don\u2019t let a \u201ctentative hold\u201d survive past next Monday.<\/li>\n<\/ol>\n\n\n\n

        How Slackbot Generated This Column<\/h2>\n\n\n\n

        To answer this question, Slackbot interpreted the natural language question about maximizing in-person Dreamforce<\/a> time and searched the account executive\u2019s Slack for relevant scheduling behavior, including planning threads, meeting coordination patterns, and Dreamforce-specific guidance shared across the org. It applied editorial judgment to select four advice points that mirrored the asker\u2019s own real habits, then blinded all account names, colleague names, and channel references before drafting the column in the Ask Slackbot voice.<\/p>\n\n\n\n

        Stealable Prompt (Account Executive):<\/h2>\n\n\n\n

        \u201cI have a list of customers attending Dreamforce this week. Pull together what you know about each account\u2019s deal stage, key stakeholders, and any live opportunities, then rank them by priority for in-person time. For my top five, draft a short confirmation message I can send to lock in the meeting, and flag any two meetings on my calendar that are scheduled less than 30 minutes apart in different locations.\u201d<\/p>\n\n\n\n