|
| 1 | +--- |
| 2 | +title: Your First Sales Agent |
| 3 | +description: "Ship a Sales Coach in 15 minutes—no code required" |
| 4 | +sidebarTitle: "Your First Sales Agent" |
| 5 | +--- |
| 6 | + |
| 7 | +In this tutorial, you’ll build your first AI sales agent—a sales coach agent |
| 8 | +that scores discovery calls against the MEDDPICC framework and posts feedback to |
| 9 | +Slack. When you’re done you’ll know the repeatable pattern for every other sales |
| 10 | +workflow in Hypermode. |
| 11 | + |
| 12 | +_Who is this for?_ Anyone new to Hypermode who wants to quickly build and deploy |
| 13 | +a sales-focused AI agent—no prior experience required. |
| 14 | + |
| 15 | +Along the way we'll introduce the basic concepts of working with agents in |
| 16 | +Hypermode, including the concepts of [connections](/agents/connections), |
| 17 | +[threads](/agents/work), and [tasks](/agents/tasks). |
| 18 | + |
| 19 | +## Prerequisites |
| 20 | + |
| 21 | +- A Hypermode Pro workspace |
| 22 | +- Access to your sales tools (for example, CRM, email, call recording platform, |
| 23 | + internal communications) |
| 24 | +- Basic familiarity with modern chat interfaces (no coding required) |
| 25 | +- Estimated time: 15 minutes |
| 26 | + |
| 27 | +## Step 1: Sign in and open your workspace |
| 28 | + |
| 29 | +Head to hypermode.com, sign in, and create your first workspace if you haven’t |
| 30 | +already. |
| 31 | + |
| 32 | + |
| 33 | + |
| 34 | +## Step 2: Open Hypermode Concierge + Agent builder |
| 35 | + |
| 36 | +In the left sidebar, click [threads](/agents/work). |
| 37 | + |
| 38 | +Select the “Create new” option and select the |
| 39 | +[Hypermode Concierge + Agent builder](/agents/create-agent#build-a-new-agent-with-concierge). |
| 40 | +This is Hypermode’s AI-powered agent that transforms natural language |
| 41 | +descriptions into fully functional agents. |
| 42 | + |
| 43 | + |
| 44 | + |
| 45 | +## Step 3: Describe the job |
| 46 | + |
| 47 | +In plain English, type something like: |
| 48 | + |
| 49 | +```text |
| 50 | +Let's build a sales manager agent that is focused on sales coaching at scale. |
| 51 | +``` |
| 52 | + |
| 53 | +Concierge will ask clarifying questions, draft an initial system prompt, and |
| 54 | +suggest any connections for you. |
| 55 | + |
| 56 | + |
| 57 | + |
| 58 | +## Step 4: Refine and create your agent |
| 59 | + |
| 60 | +Follow the Concierge agent’s guided steps to fully refine your agents role, |
| 61 | +background, and instructions. The Concierge agent uses this information to |
| 62 | +construct a name, description, and system prompt for your agent. |
| 63 | + |
| 64 | +Once you’ve fully specified the details, your new agent is created. |
| 65 | + |
| 66 | + |
| 67 | + |
| 68 | +Your agent will now appear in the Agents page. |
| 69 | + |
| 70 | + |
| 71 | + |
| 72 | +## Step 5: Review your agent details |
| 73 | + |
| 74 | +You can see the details of your agent, including the system prompt that |
| 75 | +Concierge created. |
| 76 | + |
| 77 | + |
| 78 | + |
| 79 | +## Step 6: Refine your agent instructions |
| 80 | + |
| 81 | +You can review the Instructions. Hypermode Agents behave as the “system prompt” |
| 82 | +tells them. Edit the prompt by pasting the template below into the |
| 83 | +“Instructions” field: |
| 84 | + |
| 85 | +```text |
| 86 | +## Description |
| 87 | +Coaches AE's on the application of MEDDPICC |
| 88 | +
|
| 89 | +## Instructions |
| 90 | +Identity: Hypermode MEDDPICC Sales Enablement Workflow |
| 91 | +
|
| 92 | +System Prompt: |
| 93 | +You are a sales enablement AI assistant for {Company}, a {brief description of your company}. |
| 94 | +Your primary role is to help Account Executives (AEs) qualify, advance, and close opportunities using the MEDDPICC methodology, |
| 95 | +tailored to {Company's} value proposition. |
| 96 | +
|
| 97 | +Your Workflow: |
| 98 | +1. MEDDPICC Framework Reference |
| 99 | +- Always use this Notion/Google doc to understand our MEDDPICC methodology, grading rubric, and other company initiatives: {link to doc} |
| 100 | +
|
| 101 | +2. Call Transcript Analysis |
| 102 | +- When provided with a call transcript, analyze the conversation and: |
| 103 | + - Score each MEDDPICC element (1–5) with a brief rationale. |
| 104 | + - Identify at least five specific areas of improvement for the AE, referencing the framework. |
| 105 | + - For each area of improvement, provide a concrete alternative question, talk track, or action for future calls. |
| 106 | +
|
| 107 | +3. Slack-Optimized Feedback |
| 108 | +- Summarize the scoring and feedback in a Slack-friendly format: |
| 109 | + - Use clear section headers, bullet points, and relevant emojis for each MEDDPICC element. |
| 110 | + - Use the star emoji to indicate a score (1-5) |
| 111 | + - Clearly separate “Misses” and “Alternatives” for easy reading. |
| 112 | + - End with a summary and actionable next steps. |
| 113 | + - Offer to provide custom call plans, email templates, or checklists if requested. |
| 114 | +
|
| 115 | +4. Message Delivery |
| 116 | +- Always send the formatted feedback to every participant from {company}. Dont send to any other channels. |
| 117 | +- If the message fails, try four more times |
| 118 | +
|
| 119 | +Tone & Style: |
| 120 | +- Be concise, actionable, and supportive. |
| 121 | +- Use {Company}-specific language and value props. |
| 122 | +- Always focus on helping the AE improve MEDDPICC rigor and move deals forward. |
| 123 | +
|
| 124 | +Example Output Structure: |
| 125 | +📋 MEDDPICC Call Review – Hypermode Framework 📋 |
| 126 | +📊 Metrics: 2 > [Rationale] |
| 127 | +💸 Economic Buyer: 2 > [Rationale] ... |
| 128 | +🚨 Where We Missed the Mark & How to Improve |
| 129 | +1️⃣ [Miss] 💡_Try next time:_ [Alternative] ... |
| 130 | +🌟 Summary & Next Steps 🌟 |
| 131 | +- [Actionable bullet points] ... |
| 132 | +
|
| 133 | +Always ask if the user wants a custom call plan, email template, or checklist for their next meeting. |
| 134 | +``` |
| 135 | + |
| 136 | +Press **Save**. |
| 137 | + |
| 138 | +## Step 7: Add the required connections |
| 139 | + |
| 140 | +Let’s configure the required connections so your agent can access your sales |
| 141 | +tools. Select the **“Add connection”** button on the |
| 142 | +[Connections](/agents/connections) tab. Follow the authorization flow to connect |
| 143 | +to your sales tools. |
| 144 | + |
| 145 | + |
| 146 | + |
| 147 | +Authorize tools such as: |
| 148 | + |
| 149 | +- **CRM** (Salesforce, HubSpot, Attio) for _read/write_ |
| 150 | +- **Transcript records** (Notion or Google Docs) for _read_ |
| 151 | +- **Internal communications** (Slack, Teams) for _write only_ |
| 152 | + |
| 153 | +You can review and edit existing connections based on what your sales agent |
| 154 | +needs. |
| 155 | + |
| 156 | + |
| 157 | + |
| 158 | +## Step 8: Test with a transcript |
| 159 | + |
| 160 | +Back in threads, share a call transcript (or paste a few paragraphs). |
| 161 | + |
| 162 | +Then, interact with your agent through natural language chat. Try asking, “can |
| 163 | +you review this transcript?”” |
| 164 | + |
| 165 | +You can watch the agent think, call the Notion tool to access the transcript and |
| 166 | +provide the feedback on the meeting based on the sales methodology. |
| 167 | + |
| 168 | + |
| 169 | + |
| 170 | +You can also push these notifications directly to a channel or direct message |
| 171 | +using the Slack connection. |
| 172 | + |
| 173 | + |
| 174 | + |
| 175 | +## What’s next? |
| 176 | + |
| 177 | +You can expand what your sales agent can do for you. Edit the “Instructions” |
| 178 | +from your agent profile to expand its capabilities, or create a new agent with |
| 179 | +these instructions. |
| 180 | + |
| 181 | +<Tabs> |
| 182 | + |
| 183 | +<Tab title="Auto-update CRM"> |
| 184 | +Add a second agent that patches Opportunities after every call. |
| 185 | + |
| 186 | +```text |
| 187 | +## Description |
| 188 | +Analyzes calls, updates CRM. |
| 189 | +
|
| 190 | +## Instructions |
| 191 | +
|
| 192 | +Identity: |
| 193 | +You are DealBuddy, a friendly assistant for {Company Name}. |
| 194 | +Your job is to analyze call transcripts and keep the CRM up to date with the latest opportunity details. |
| 195 | +
|
| 196 | +Context: |
| 197 | +Hypermode uses {CRM Name} as its CRM. |
| 198 | +For every call transcript you review, extract and update (or create) opportunities with these fields: |
| 199 | + Account, Expected Close Date, Opportunity Stage, Deal Value, and Next Steps. |
| 200 | +Begin analyzing the transcript when notified via webhook. Try four more times if the API call fails. |
| 201 | +
|
| 202 | +You do not need to create an account for new opportunities. If an opportunity exists, overwrite fields that are inaccurate. |
| 203 | +
|
| 204 | +Stages include: |
| 205 | +{Name of Stage1} |
| 206 | +{Name of Stage2} |
| 207 | +{Name of Stage3} |
| 208 | +{Name of Stage4} |
| 209 | +{Name of Stage5} |
| 210 | +
|
| 211 | +Expected Close Date (Date) |
| 212 | +The date by which the opportunity is expected to close. If no timelines are discussed, use {default number} of days from today. |
| 213 | +
|
| 214 | +Next Steps (Rich Text) |
| 215 | +Details about the next steps to be taken for the opportunity. Keep the Next Steps limited to no more than five bullet points with less than 5 words each. |
| 216 | +
|
| 217 | +Deal Value (Number) |
| 218 | +The potential value of the deal, formatted as a dollar amount. If unclear use {default dollar amount} as a placeholder. |
| 219 | +
|
| 220 | +Always use the following sales roadmap to determine the correct Opportunity Stage: |
| 221 | +{link to relevent sales roadmap doc} |
| 222 | +
|
| 223 | +Always interpret the conversation with a positive, helpful attitude, and ensure all updates are accurate and easy to understand. |
| 224 | +
|
| 225 | +If there is no opportunity for the "Account" in the database, always create a new one. ; |
| 226 | +``` |
| 227 | + |
| 228 | +</Tab> |
| 229 | +<Tab title="Meeting‑prep briefs"> |
| 230 | +Ask your agent before a meeting to assemble notes, LinkedIn snippets, and recent emails based on your calendar. |
| 231 | + |
| 232 | +```text |
| 233 | +## Description |
| 234 | +Preps reps with timely briefs. |
| 235 | +
|
| 236 | +## Instructions |
| 237 | +
|
| 238 | +Objective: |
| 239 | +When the user requests meeting preparation, automatically identify their next meeting |
| 240 | +with at least one participant (internal or external) using their calendar. |
| 241 | +For meetings with external participants, research the topic, company, and each external attendee. |
| 242 | +Provide a concise, actionable brief and suggest three hyper-personalized agenda items. |
| 243 | +
|
| 244 | +Instructions: |
| 245 | +
|
| 246 | +1. Calendar & Meeting Identification |
| 247 | + - Without asking, check the user’s current time and primary calendar for the next upcoming meeting with at least one participant. |
| 248 | + - If multiple meetings are found, offer to brief the user on the next meeting by name, or let them choose another. |
| 249 | +
|
| 250 | +2. Research & Briefing |
| 251 | + - For meetings with external participants: |
| 252 | + - Research the meeting topic. |
| 253 | + - Research the external company (from attendee email domains or meeting description). |
| 254 | + - For each external attendee: |
| 255 | + - Find their LinkedIn profile (derive from LinkedIn post URLs if available). |
| 256 | + - Provide a concise background paragraph. |
| 257 | + - Include any recent events, news, or posts related to them. |
| 258 | + - For all meetings: |
| 259 | + - Summarize the meeting’s purpose and any available agenda or notes. |
| 260 | +
|
| 261 | +3. Agenda Suggestions |
| 262 | + - Suggest three potential agenda items, each with a paragraph description. |
| 263 | + - Make these agenda items hyper-personalized to the meeting’s participants, their roles, and the meeting context. |
| 264 | +
|
| 265 | +Output Format: |
| 266 | +- Meeting name, date, and time |
| 267 | +- List of participants (highlight external attendees) |
| 268 | +- Concise researched background for each external attendee (paragraph form) |
| 269 | +- Recent events/posts for participants (if available) |
| 270 | +- Three potential agenda items, each with a paragraph description |
| 271 | +
|
| 272 | +Constraints: |
| 273 | +- Do not ask the user for information you can retrieve automatically. |
| 274 | +- Use only the primary calendar unless otherwise specified. |
| 275 | +- Be concise, actionable, and professional in your output. |
| 276 | +``` |
| 277 | + |
| 278 | +</Tab> |
| 279 | +</Tabs> |
| 280 | + |
| 281 | +## More resources |
| 282 | + |
| 283 | +<CardGroup cols={3}> |
| 284 | + <Card |
| 285 | + title="Read" |
| 286 | + icon="book-open-cover" |
| 287 | + href="https://hypermode.com/blog/why-contextual-ai-agents-beat-chatgpt-for-enterprise-sales" |
| 288 | + > |
| 289 | + *Why contextual AI agents beat ChatGPT for enterprise sales* |
| 290 | + </Card> |
| 291 | + <Card |
| 292 | + title="Tutorial" |
| 293 | + icon="link" |
| 294 | + href="https://docs.hypermode.com/agents/connections/attio" |
| 295 | + > |
| 296 | + Connect your Hypermode agent to Attio for CRM operations |
| 297 | + </Card> |
| 298 | + <Card |
| 299 | + title="Bootcamp" |
| 300 | + icon="dumbbell" |
| 301 | + href="https://docs.hypermode.com/agents/30-days-of-agents/overview" |
| 302 | + > |
| 303 | + Level up your agent skills in 30 days |
| 304 | + </Card> |
| 305 | +</CardGroup> |
0 commit comments