Skip to content
AgentSDR
Star

For sales teams

The open-source sales engagement platform for teams

Every rep sends from their own mailbox, LinkedIn account and WhatsApp number. Every reply lands in one shared queue, in one pipeline, with limits that protect each account separately.

Star on GitHubSelf-host it
Reps and their accounts
PN

Priya Nair

Owner
  • priya@…
  • Priya Nair
  • +91 80 0000 0101
MB

Marcus Bell

Member
  • marcus@…
  • Marcus Bell
  • +44 20 0000 0102
ER

Elena Ruiz

Member
  • elena@…
  • Elena Ruiz
  • +34 91 000 0103
Action required · shared4

  • Hannah Cole · Fernwood

    via Marcus

    “Happy to see a demo next week.”

    Demo Requested

  • Ravi Menon · Oakline

    via Priya

    “Can you share a case study?”

    Information Requested

  • Sofia Marin · Tidewater

    via Elena

    “Not right now, maybe in Q3.”

    Not Required Right Now

  • Ian Prescott · Brightloom

    via Marcus

    “Looping in our ops lead.”

    Connected to Different POC

Everyone in the organization sees the same queue. An illustration with sample data.

How a team works

Individual accounts, shared work

Reps keep their own sender identity. The leads, the pipeline and the queue belong to the whole organization.

  • Owner, admin and member roles

    Roles control what a person can change: integrations, AI, rules, people. Everyone can use the product.

  • Teams to group reps

    Outbound, Account executives or any grouping you like. Teams organise people; they do not split the data.

  • Per-rep accounts

    Mailboxes, LinkedIn accounts and WhatsApp numbers, each with its own status and working hours, and its own daily limit on LinkedIn and WhatsApp.

  • One lead database

    A person is one record across channels, so two reps never write to the same lead from different tools.

  • One Action required queue

    Replies from every rep's accounts, classified and drafted, in a single list you can filter by channel.

  • Do Not Contact for everyone

    One flag stops email, LinkedIn and WhatsApp, and it is re-checked before each send.

Per-rep accounts

Pace every account on its own

One rep’s LinkedIn limit is not another rep’s. Limits live on the account, with organization rules behind them.

Account limits

Account limit, then organization rule, then default

Set the Sending rules once for the organization. When one account needs less, or more, give it its own limit and it replaces the rule for that account only.
  • A mailbox's own sending hours
  • A LinkedIn account's own daily invitations
  • A WhatsApp number's own new chats a day
Invitations per day

Elena Ruiz

  1. 1

    Account's own limit

    Set on LinkedIn, Accounts

    not set
  2. 2

    Organization rule

    Settings, LinkedIn, Sending rules

    not set
  3. 3

    Built-in default

    Premium or Sales Navigator

    30
30invitations a day for Elena

The organization’s value of 25 is an example, not a default. An illustration with sample data.

LinkedIn

Runs, gaps and rests, per account

Each LinkedIn account sends in short runs with random delays between invitations and a rest between runs, inside its own working hours. Premium and free accounts get different daily defaults.
  • 30 invitations a day on Premium or Sales Navigator, 5 on free
  • A random 30 to 60 second delay between invitations
  • Several accounts working one campaign

Roles

Who can change what

Roles never change what a person can see, because everyone in an organization sees the same leads, campaigns and conversations. They decide who can connect services, change rules and manage people.

Owner
  • Everything an admin can do
  • Promote someone to owner
  • Change or remove an owner
  • The last owner cannot be demoted or removed
Admin
  • Connect and edit integrations
  • Change AI settings and sending rules
  • Invite people and change roles
  • Create and manage teams
Member
  • Use leads, campaigns and the CRM
  • Work Action required and Analytics
  • See the same data as everyone else
  • See sending rules and settings, read-only

Shared pipeline

One queue, one pipeline, one scoreboard

Whoever’s account a lead answered on, the reply reaches the same Action required queue and moves the same pipeline.

Action required

Every rep’s replies, classified and drafted

The AI puts each reply in a category, records its confidence and drafts an answer from your instructions and knowledge base. Anyone on the team can review and send; nothing goes out unapproved.
  • Filter by channel, category, due time or sequence
  • Drafts go out from the account the conversation is on
  • Reply sequences wait for a person's approval
Analytics shows replies, meetings and customers by channel, for the whole organization.
agentsdr.your-company.com/analytics

Analytics

How conversations turn into meetings and customers, and which channels bring them in.

Last 4 weeks

Replies

512

17.2% improved versus the previous period

from 386 people

Positive

104

25.3% improved versus the previous period

27% of people who replied

Meetings

37

27.6% improved versus the previous period

vs 29 previous period

Customers

6

50% improved versus the previous period

vs 4 previous period

Median first response

38m

46.5% improved versus the previous period

vs 1h 11m previous period

Replies by sentiment

Inbound replies each day, by the category they were classified into.

  • Interested

    132

  • Customer

    12

  • Not interested

    95

  • Other

    80

  • Unclassified

    4

Needs attention

Right now, regardless of the date range.

Pipeline now

Open records by category, right now, and how far along the funnel they are.

  • Interested10350%
  • Customer94.3%
  • Not interested6431%
  • Other2713%
  • Unclassified52.4%

Funnel stages · darker as they advance

  • Information Requested · Interested41
  • Demo Requested · Interested18
  • Meeting Requested · Interested22
  • Meeting Done · Interested15
  • Trial User · Interested7
  • Customer · Customer9

Stage moves this period

Records moved into a new stage, by the category they moved into.

  • Interested9249%
  • Customer63.2%
  • Not interested5831%
  • Other3117%

Top stages

  • Not Required Right Now · Not interested58
  • Information Requested · Interested46
  • Out of Office · Other31
  • Meeting Requested · Interested29
  • Demo Requested · Interested17

Workflow

Every record by workflow state, right now.

  • Paused92%
  • Action required235.1%
  • Waiting11826%
  • Closed8719%
  • Idle20446%
  • Other (2)71.6%

AI assistant

262 drafts generated in this period.

11 awaiting review

Drafts sent

214

27.4% improved versus the previous period

AI drafts that went out

Classified

498

18.3% improved versus the previous period

Replies the AI labelled

Override rate

6.4%

29.7% improved versus the previous period

Labels a person changed

71% of sent drafts went out unedited (151 of 214)

  • Sent as-is

    151 62%

  • Sent edited

    63 26%

  • Discarded

    29 12%

Outreach

Where these conversations came from. Open a channel for its detail.

Channels

How each channel performed in this period. Select a row to open it.

Channel comparison
ChannelReachedRepliedReply ratePositiveOpen
2,874118
4.1%
29
1,902171
9%
47
54297
18%
28

Conversion funnel

From first touch to customer.

  1. Reached
    5,318
  2. Replied
    7.3%386
  3. Positive
    26.9%104
  4. Meeting
    35.6%37
  5. Customer
    16.2%6

Counts for this period — not one cohort followed through.

Rolling it out

From first admin to a working team

  1. 01

    Run it and create the organization

    The first account creates the organization and becomes its owner.
  2. 02

    Invite reps

    Settings, Members: send an invitation with a role, valid for 7 days. Group reps into teams if it helps.
  3. 03

    Connect accounts

    Each rep's mailbox, LinkedIn account and WhatsApp number, with its own LinkedIn or WhatsApp limit where it needs one.
  4. 04

    Launch and share the queue

    Campaigns send from the accounts you choose, and every reply lands in the shared Action required.

FAQ

Questions, answered

Can each rep use their own mailbox, LinkedIn and WhatsApp account?

Yes. Mailboxes are added by address, LinkedIn and WhatsApp accounts are linked in Unipile and synced in, and each account has its own status and limits. Campaigns send from whichever accounts you choose, and replies show which account they came through.

What can members, admins and owners do?

Everyone can use leads, campaigns, the CRM and Analytics. Owners and admins also connect integrations, change AI settings and sending rules, invite people and manage teams. Only owners can promote someone to owner or change an owner.

Do teams limit what a rep can see?

No. Teams group people, for example Outbound or Account executives, but everyone in an organization sees the same leads, campaigns and conversations. If two groups must not see each other's data, run them as separate organizations.

How do per-account limits work with the organization's sending rules?

A limit resolves in order: the account's own override, then the organization's rule, then the built-in default. Overrides exist for a LinkedIn account's daily invitations and a WhatsApp number's new chats a day. A mailbox takes its daily limit from the organization rule when it is added, and has its own sending hours. Only owners and admins can change rules.

Is there a shared pipeline and reply queue?

Yes. The organization has one default CRM pipeline, and Action required lists every reply, AI draft, follow-up and error waiting on a person, across email, LinkedIn and WhatsApp. Replies are classified by the AI, and nothing is sent until someone approves it.

How much does it cost per seat?

Nothing. AgentSDR is open source under the AGPL-3.0 and you host it yourself, so there are no per-seat or per-contact fees. You pay for your server, the accounts you connect and your own AI usage.

Keep exploring

Give every rep an account, and the team one queue

Self-host AgentSDR, invite your reps and keep each account inside its own limits. No seats, no per-contact fees.

Star on GitHubSelf-host it