Outbound Tool Capacity: Understand Seats, Mailboxes, and Phone Numbers
Count user seats, sending mailboxes, calling numbers, and metered usage separately when reading an outbound plan. A seat is access for a person; a mailbox is a sending resource; a calling number is an identity and routing resource; usage covers work performed. The quantities can be related by a plan, but they are not the same unit.
Before comparing prices, map the work your team intends to do to the resources it requires. Then verify the included quantities, assignment rules, limits, and billing cycle in the current plan and workspace. A feature listed on a pricing page does not establish that every user has every resource provisioned and ready.
Start with the unit being sold
| Unit | What it represents | What to verify separately |
|---|---|---|
| User seat | A person's access to the product and included capabilities | Role, paid entitlement, and feature availability |
| Sending mailbox | An email account connected or managed for sending | Ownership, allowance, readiness, and capacity |
| Calling number | A number assigned for outbound caller identity and callbacks | Per-user allowance, location, recurring cost, and forwarding |
| Metered usage | Work consumed through supported activities | Rates, allocation, renewal, and exhaustion behavior |
Read “per seat,” “per rep,” and “per workspace” literally. A per-workspace pool and a per-user allowance can produce different constraints even if the overall quantity appears similar. Record the unit beside every quantity in your comparison.
A seat controls access, not every downstream resource
A seat answers who can use the product under the plan. It does not by itself establish the user's permissions or whether a mailbox and calling number have been configured. Review Unify's members and roles documentation when determining what each intended user needs to do.
The current pricing page distinguishes plan capabilities, seat terms, mailbox entries, and credit allocations. Some capabilities are plan-specific. The relevant question is whether the proposed plan covers your workflow, not simply whether it permits another login.
Separate the people who perform outreach from administrators, managers, and other users who need access. Confirm the applicable commercial treatment for each rather than assuming every role is free or every person must have the same capabilities. Use your workspace's actual plan evidence to settle those details.
A mailbox is a sending account with its own operating state
Unify supports connected work mailboxes and Unify-managed mailboxes. Their setup and management paths differ. Count the type required by the workflow, not just the number of email addresses visible in a spreadsheet.
The pricing table currently includes mailbox entries by plan and separately describes managed-mailbox availability. Verify the exact entitlement and any additional capacity in the workspace before assuming an included mailbox entry means a newly provisioned managed account. “Included,” “connected,” “assigned,” and “ready to send” describe different states.
Use mailbox operations to inspect assignment, connection, warmup, and reply routing. A mailbox assigned to a user can still be paused, unauthorized, or not ready for the intended volume. A paid entitlement is not proof that the resource is operational.
Mailbox groups organize sending resources, but grouping does not create new capacity. Confirm which mailboxes are actually eligible for the planned enrollment and who owns their replies.
Mailbox count is not the same as sending capacity
Unify's sending-limit documentation explains that sequences sharing a mailbox share its capacity. First touches and follow-ups both consume that capacity. Current capacity can also differ from the configured maximum while a mailbox is ramping.
A send schedule controls when eligible work can run. It does not increase the mailbox's allowance. The number of seats therefore cannot be multiplied by an assumed daily send figure and treated as guaranteed throughput.
Record ready capacity and existing workload for the same planning window. Keep unavailable or warming mailboxes separate from ready resources. If the team has no ready senders, report that constraint rather than substituting the quantity purchased or requested.
Calling numbers are distinct from prospect phone data
An assigned outbound number is the number prospects see when your rep calls. A prospect's phone number is a destination the rep wants to reach. Paying to enrich a prospect's phone number is not the same as obtaining or maintaining an outbound calling number.
The dialer setup guide requires an active workspace dialer and an assigned number for calling. Administrators can assign numbers, and users can configure a callback destination. The callback number is another role: it is where return calls to the assigned Unify number are forwarded.
The dialer pricing reference documents per-rep number allowances, additional-number costs, and connected-time usage. Verify the current allowance for the selected user before adding a number. Number location and international calling requirements can affect what is available.
This article defines the units; the separate dialer cost guide addresses the cost structure in more detail. Do not infer unlimited calling from included access to a dialer or an included number.
Usage is a separate dimension of capacity
Unify's credits and usage guide describes consumption across prospecting, enrichment, research, chat, signals, and calling. Review the displayed rates and allocation for your workspace. A single workflow can use several capabilities, so counting only the number of users does not describe its consumption.
Keep the credit cycle and the reporting date range aligned when reviewing usage. The guide notes that a chart filtered to a different period or workflow can differ from the cycle balance. That difference does not necessarily indicate a billing error.
Record whether an allowance renews, is pooled, is attached to a user, or comes from a separate purchase. Confirm what happens when it is exhausted and who can purchase additional capacity. After a resource is restored, inspect the affected workflow for any required recovery action instead of assuming that every blocked step has completed.
Build a people-to-resource inventory
Copy the following blank inventory for each intended user or role. Record observed entitlements only after reviewing the plan and workspace. Keep a dated evidence reference so the inventory can be checked again when a plan or assignment changes.
| Inventory field | Required resource or behavior | Verified entitlement and evidence |
|---|---|---|
| Intended user or role | ||
| Required product access and permissions | ||
| Seat unit and applicable plan | ||
| Connected or managed sending mailbox | ||
| Mailbox allowance, assignment, and readiness | ||
| Required sending window and existing workload | ||
| Assigned calling number and location | ||
| Number allowance and recurring charge basis | ||
| Callback destination and owner | ||
| Enrichment, research, chat, or calling usage | ||
| Allocation unit, renewal cycle, and top-up rules | ||
| Plan evidence date and unresolved dependencies |
The inventory is an operating worksheet, not an assertion that every plan includes one of each resource. Leave unsupported quantities unresolved and request the exact entitlement rather than inferring it from a general marketing phrase.
Move from resource definitions to a budget
Once the inventory is complete, consolidate identical resource units and check which are already included. Keep one-time setup, recurring resources, and variable usage separate. Avoid counting a resource twice because it appears both in a bundled feature list and a workspace inventory.
Use the outbound startup-budget guide for the broader budget and the contract-flexibility guide for changes in seat commitments. Those decisions become easier when “seat,” “mailbox,” and “number” already mean something precise in the working inventory.
Before signing or expanding, have the operator confirm the resources required and the billing owner confirm the entitlement. Resolve any mismatch between intended work and available resources. A low displayed seat price is not a complete capacity plan.
Frequently asked questions
Does buying a seat automatically provide a ready sending mailbox?
Not necessarily. Check the plan's mailbox entitlement, whether the account is connected or managed, its assignment, and its operating state. Access, provisioning, and readiness are different questions.
Is an outbound calling number the same as an enriched phone number?
No. The assigned outbound number identifies the caller and supports callbacks. An enriched prospect number is a destination to call. They can have separate entitlements and costs.
Does an included dialer mean unlimited calling?
No. Verify number allowances and metered call usage separately. Unify documents connected-time consumption and plan-dependent number allowances.
What should a resource inventory contain?
List each intended user's access, mailbox type and readiness, calling-number requirements, callback ownership, metered activities, allocation rules, and dated plan evidence. Keep unresolved entitlements visible.

