Email · 8 min read
A shared address needs shared visibility and clear ownership, not a password passed between colleagues. Otherwise two people answer the same request or both assume someone else will.
Explore this workflow in Moove.
A sales or support address represents a service. Each team member should access it through an individual account with permissions suited to their responsibilities.
Plan access removal when someone leaves without losing business history. Avoid sharing a personal mailbox to solve a team workflow.
Use a queue and agreed status definitions so people can tell what is waiting, in progress or answered. Assignment helps coordination, but the team still needs rules for handoffs and absences.
A numbered reference helps people locate a request across conversations and records. Document what receives a number and whether replies belong to the same thread.
A reference is not an SLA guarantee or proof that a request was resolved. Confirm the actual outcome before closing it.
Link relevant conversations to the correct customer or opportunity. Check identity and permissions rather than assuming an email address always identifies one person.
Keep restricted information out of unrelated records. CRM linking should preserve context, not make private conversations visible to everyone.
A shared inbox succeeds when each request has ownership, traceable context and controlled access.
Not necessarily. Connection options depend on the provider and account settings. Verify the supported method before making a change.
No. Clear workflow and collision handling still matter. Test the behavior with your team.
No. It identifies a record; resolution requires confirming the outcome.
Prefer an address intended for the team and separate permissions. Review personal information before any migration.
Teste grátis por 7 dias, sem cartão, ou fale agora com um especialista.