Plan the reply after the post
Comments and messages can include sales questions, support needs, or sensitive information. Decide who responds, when an issue moves to another channel, and what should never be handled in a public reply. Leave the team with a decision, an owner, and a review date.
Show the process, explain a decision, answer a customer question, or demonstrate an offer. Each post should have a purpose beyond repeating the service name. Review recent inquiries before making assumptions about demand.
Community responsibilities
Agree who answers comments and private messages, how quickly, and when issues are escalated. A public complaint or sensitive request should have a defined handling process. Name an owner for each task so requests do not get lost.
Organic publishing and paid distribution serve different purposes. Separate content production, account management, and media spend when agreeing scope. Give the team a clear route for questions and corrections.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities