See what your tool can already connect to
Every tool in this bootcamp can connect to more than most organizations have switched on, such as email, a CRM, shared files or a reporting system. Often nobody has asked yet. Look at what your tool offers and make a list.
Open Settings, then Plugins (some accounts say Apps). Note the apps that would help your recurring work, and any marked Disabled by admin.
In the sidebar, select Customize, then Connectors, and browse the directory. On Team and Enterprise plans an Owner adds connectors for everyone, so you may see Request beside one you can't use yet.
With a Microsoft 365 Copilot licence, select ⋯, then Settings, then Sources to see the connectors your organization offers. Copilot Chat without that licence doesn't connect to other apps, so the capability worth asking about may be the licence itself, for you or one team.
Type @ in a chat to see the Google apps Gemini can use, such as Google Drive and Google Calendar, or select Customize, then Connectors (some accounts say Connected Apps). Your Workspace admin turns these on or off for everyone.
Write down two or three you'd use, in a sentence each. You'll need the list in the next step.
Pick the one that would change your work most
In the video, I give a few examples: a sales team whose agent adds call notes to the CRM, a finance team running analysis straight from the data warehouse, and anyone whose agent could work from their email. Pick the one that matters most for your recurring work. One clear ask gets further than five.
Open a chat in My Agent, or a new chat if you don't have one, and send this card with your list from step 1. Describe your work at the level the data rules allow.
I want to ask my IT team to switch on one capability in my AI tool that would change how I work. Help me choose it. Don't connect, install or send anything. What my tool offers that I can't use yet, or I'm not sure I'm allowed to use: [list what you saw, such as Gmail, Salesforce, SharePoint or a Microsoft 365 Copilot licence] The recurring work I'd like my agent to help with: [describe it in a sentence or two] Where the information for that work lives today: [such as my inbox, our CRM, a shared drive or a reporting system] Ask me up to three questions, one at a time, if you need more. Then recommend the one capability that would save the most time or make the biggest difference to a business result, and say why in two or three sentences. Name the other people or teams in my organization who would benefit if it were approved. Use only what I've told you. Don't add numbers, savings or features I didn't give you, and mark anything you're unsure about with [CHECK].
Answer its questions, then check the recommendation against your own work. If it names something you'd rarely use, tell it so and ask for the next one.
Check what your organization has already decided
Work within your company's guidelines. If your organization has clearly said no, respect it. Most haven't decided yet, because nobody has started the conversation.
Check your AI policy or approved-tools list, and your Safety & Security Rules, for your pick. Then follow the case that fits.
Already approved
Follow your IT team's instructions for turning it on, and skip the request in the next step.
Clearly not allowed
Leave it. Go back to step 2 and ask your agent for the next option. If everything on your list is ruled out, go on to the next step anyway. Your request there asks what's approved or planned, instead of asking for one.
Not decided, or you can't tell
This is the usual case. Find who approves new tools, such as your IT help desk, your security team or an AI committee, and go on to the next step.
Write your request to IT and security
Asking can feel uncomfortable if you don't work in IT. A short, specific request is easier to say yes to. It names the capability, the business reason and one small test: one person or team, read-only where the tool allows, for a few weeks, then a report back.
In the same chat, send this card. For the decision, write something like approve a four-week test of [the capability] for [me or my team], and for where it will go, a help desk ticket or an email. In your notes, add the reason from step 2, what you checked in step 3, and your questions, such as what it can reach and change.
Task: Help me write a request that gets a clear decision from the person who approves it. Interview me first, then draft it. Don't send or post anything. Context: - The decision I need: [your decision sentence: approve what, by when] - Who decides: [their role, such as my director or the department head, and what they care about most, if you know] - Where it will go: [an email, a Teams or Slack message, or a one-page memo] - Setting: [a My Voice Dial setting if you have one, or leave this blank] - My notes: [paste your notes here] Interview: Ask me up to five questions, one at a time, about things my notes don't cover that this person would need to know before saying yes, such as the cost, other options, the risk of doing nothing, who else it affects, or how we'd know it worked. Wait for each answer. Never send a list of questions. If I say I don't know, mark it [CHECK] and move on. Constraints for the draft: - If my Agent Profile is here, use it for background. Use my Communication Style Guide and the setting I named for how I write, and my default rules if I named none. If you can't see my style guide, write plainly and directly, and tell me at the end that you didn't have it. - Say what I need decided, and by when, in the first two sentences. - Then give the reason, the cost in money, time or people, and the options I considered, including doing nothing. - End with what happens next if they say yes, from my notes or answers. - If it's going by email, suggest a subject line that names the decision. - Use only facts I gave you. Don't add numbers, savings, dates, benefits or names I didn't give you. Where a fact is missing, write [CHECK: what's needed]. - Fit the length to where it will go. A busy reader should get the ask from the first two sentences alone. Output check, after the draft: 1. Everything you marked [CHECK]. 2. Any claim in the draft that rests on my opinion rather than a fact I gave you. Start with your first question.
Read the draft before you send it. Every fact should be yours, with no promised results you can't back up, and it should ask for a test, not everything at once. Then send it yourself, through your help desk or usual channel.
If everything on your list was ruled out in step 3, write the decision as tell me which AI capabilities are approved or planned for [my team], and add your list and your recurring work to your notes.
For more on getting a clear yes, see Write the Ask Your Boss Can Say Yes To.
Keep asking, and bring others with you
If the answer is yes, run the small test and share what you learn with your team. One approval can change how dozens of people work. If it's not yet, ask what would change the answer, and keep working with files meanwhile.
Then keep going. Your 30-day plan from Make Your Agent Part of How You Work keeps your agent in your weekly work, and the Field Guides have more ideas when you're ready.
You still have this site for several weeks after the bootcamp, and you still have me. If you get stuck on any guide, open Get help with this step and choose Ask Devon.
Confirm your result
Confirm the outcomes below to finish this guide.
Final checks
You've chosen one capability your tool already has that would change a piece of your recurring work, and checked what your organization has decided about it.
Your request is with your IT team, sent by you: a small, limited test of your pick with its business reason, or, if your whole list was ruled out, a question about what's approved or planned. If your pick was already approved, you've turned it on your IT team's way.
Provide Feedback
Thanks. That went straight to the people who write these guides.