Two teammates can answer creators without duplicating replies if each conversation has one current owner, a visible work state and a recorded handoff. Claim the conversation before drafting. Let the second teammate review internally, and transfer ownership before they send. Keep lasting relationship facts in the creator record and today's reply task in the inbox.
A shared influencer outreach inbox needs these rules even when both people can see every message. Shared visibility alone does not tell either person who should answer.
Set up access and responsibility separately
Choose one place where both teammates can see the conversation, sent replies and current owner. Decide which address each person should send from. Confirm that a reply sent by one teammate appears in the other's view before you use the inbox for live creator work.
Check whether your tool supports assignment, reassignment, internal notes and a view of unassigned conversations. These are specific capabilities to verify. For example, Google Groups documents conversation assignment and completion for Collaborative Inbox groups. Assignment requires its metadata moderation permission. Do not assume an ordinary shared email address includes the same controls.
For a two-person team, appoint one person to review new, unassigned messages during each coverage period. That person either takes a thread or assigns it to their teammate. Agree on a backup for absences. The backup takes over through a visible reassignment, rather than replying while the original owner remains responsible.
If your tool lacks assignment, keep a shared register linked to each thread and let one designated person make ownership changes. Do not let both people independently claim work in separate personal lists. If this becomes burdensome, native conversation assignment is a useful requirement for your next inbox tool.
Use states that say who acts next
The following is a recommended routing table. These labels are team conventions, not universal email-provider statuses. Map them to your tool's fields or labels without treating read/unread as a work state.
| State | Owner | Next action | Leave this state when |
|---|---|---|---|
| New, unassigned | Coverage lead until assigned | Check creator and campaign; assign a responder | A named teammate takes responsibility |
| Needs our reply | Named responder | Read context, prepare and send an answer | Reply is sent or an internal decision blocks it |
| Waiting internally | Same responder | Ask a named reviewer for a specific decision | Reviewer answers; responder resumes the reply |
| Waiting for creator | Same responder | Review on the recorded date | Creator replies or the review date arrives |
| Closed | Last responder retained | No current reply task | A new message creates work |
Keep the responder assigned while a manager approves a rate or scope change. Put the manager in a separate reviewer field or note. Otherwise a request for approval can look like a complete transfer of the creator conversation.
Add a next action and a due time to every open thread. A review date means the owner checks what needs doing. It should not trigger another message by default. Use a separate follow-up decision process when deciding whether to contact a creator again.
On a new reply, return the thread to Needs our reply. Check whether your tool does this automatically and whether it preserves the owner. If the owner is away, the coverage lead assigns the backup. A closed conversation should never disappear from responsibility merely because it received another message.
Keep relationship history distinct from inbox work
The inbox answers a narrow question: who does what next on this conversation? The creator record answers what the team knows and has agreed across conversations and campaigns.
HubSpot's activity documentation shows one example of this second function. Emails, meetings and notes can sit on a record's timeline, including interactions logged from outside the system. That history remains useful after a particular reply task ends.
Use the following division even if both views live in one application:
| Information | Place to maintain it |
|---|---|
| Current responder, work state, next action and reply deadline | Inbox conversation |
| Accepted scope, relevant past campaigns and dated decisions | Creator relationship record |
| Current draft and approval question | Internal conversation note |
| Confirmed change agreed in the thread | Creator record, linked to the supporting message |
| Request to stop outreach | Shared contact restriction that every sender checks |
Avoid copying a full transcript into several notes. Link to the conversation and record the decision that future teammates need. Label a proposal as a proposal until the creator accepts it.
The Modash Inbox article describes bringing creator context alongside messages and sharing thread ownership across a team. Use that as a product example. Your operating rule still needs to say which record owns each fact, particularly if several tools store copies.
For the broader relationship record, use the creator CRM guide. Keep this inbox setup focused on current replies.
Transfer a thread with a handoff note
A handoff is complete when the receiving teammate has accepted responsibility and can act without guessing. Until then, the outgoing owner or coverage lead remains responsible for finding coverage.
Before transferring a conversation:
- Read the latest incoming and sent messages, including related threads about the same campaign.
- Identify the creator's unanswered question and any promise your team already made.
- Link the current brief, agreed scope and relevant creator record.
- State which decision remains open and who can approve it.
- Name the next action and deadline, including the time zone.
- Review any scheduled messages and pause those that conflict with the new plan.
- Record the new owner and their acceptance before they send.
Here is an illustrative handoff for a hypothetical partnership. The names and circumstances are invented.
Conversation: Product launch, proposed video scope
Outgoing owner: Maya
Incoming owner: Leo, accepted Wednesday at 10:00 UTC
State: Waiting internally
Creator's open question: Can the proposed video become a photo carousel?
Agreed so far: No format change accepted.
Decision needed: Campaign lead to confirm whether a carousel meets the brief.
Next action: Leo gets that decision, then answers in the existing thread.
Due: Thursday at 14:00 UTC
Records: Current brief and creator record linked in the conversation.
Scheduled messages: Existing follow-up paused.Maya stops drafting once Leo accepts. Leo checks the latest thread before sending because the creator may have added information after the handoff. If the campaign lead needs more time, Leo owns the response about timing too.
Test the process before sharing live work
Use an internal test thread. Have one teammate take it, add a draft or internal note, and transfer it to the other. Confirm that both see the same owner and sent reply. Reopen the conversation with another test message and check where it appears.
Then rehearse an absence. Can the backup find the thread, see the pending decision and take responsibility without asking the absent teammate? Also check a creator with a stop-contact restriction. Follow the cross-list opt-out workflow rather than leaving that request inside a closed message.
Before either teammate presses Send, check the current owner, newest message, latest sent reply and any queued message. If two drafts exist, keep one responder and move the other person's input into an internal note.
Start with the oldest unassigned conversation in your inbox. Give it an owner, a work state and a dated next action. Ask the second teammate to identify who will answer without consulting you.
