Skip to content
agentusehub

Run business development and sourcing bots on email and Teams

The author runs multiple Grok Bot agents connected to Microsoft email and Teams accounts, including two BD agents and one sourcing agent.

Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

The author runs multiple Grok Bot agents connected to Microsoft email and Teams accounts, including two BD agents and one sourcing agent.

Reported experience

  1. What they did

    The author says they set up six Grok Bot agents, with three tied to separate Microsoft accounts so each could use email and Teams in isolation: two for business development and one for sourcing. In practice, the BD agents used browser access to log into the team’s websites, write customized outreach emails, respond to replies, send requested marketing material, and later follow up without waiting for API integrations.

  2. How it went

    The author says the communication quality felt strong enough that the agents seemed like they were actually working accounts, but the setup was hampered by daily Chrome profile resets, frequent crashes, limited concurrency of about one to two active agents, and heavy usage that burned 42% of a weekly allowance on day one.

  3. Worth knowing

    Each agent needed its own Chrome profile, and the author says usage hit about 42% of the weekly limit on the first day.

Example prompts

Try with Grok Bot
Act as a business development agent for [company]. Use the connected [Microsoft email and Teams accounts] to find new leads in [source, e.g. inbound inquiries or a target list], and draft a personalized outreach message for each. Pause and show me every draft before you send any email or Teams message. Finish with a tracker of leads, status, and next steps.