Where Should a Blog Take Comments and Questions?
Keep public comments useful to everyone and move bookings to one private channel. This pottery class example shows how to reply, check availability, and handle personal details.
A useful post still leaves readers with questions. “Do I need an apron?” belongs in a public comment because the answer may help everyone. A name, phone number, or booking detail belongs in a private conversation. Decide where each kind of question goes before replies start arriving.
Use public comments for answers everyone can use
Questions about opening hours, directions, parking, or what to bring are good candidates for a public reply. If someone asks, “Do you have aprons?” you could answer: “Yes, we have aprons. Clay can splash, so comfortable clothes are a good idea.” Other readers can use the answer too.
Keep a customer’s name, phone number, child’s name, and payment details out of public comments. Move booking questions to a private comment or the contact channel you already use. If someone has posted personal information publicly, do not quote it in your reply. Hide or remove it where possible, then point them to the private channel.
Choose one contact channel customers already know
Pick one main place for booking questions: the messaging tool linked from your profile, a Kakao channel, or your booking page. Then say where to go. For example: “For dates and reservations, message us through the Talk button on our profile. We’ll keep directions and what to bring in the comments.”
When comments, personal accounts, texts, and several chat apps are all open, two people can give different answers about the same booking. If more than one person replies, assign an owner for the day and keep availability in one shared place. That makes it less likely someone confirms two seats in the morning after they have already filled.
Automate the repeated details, keep decisions with a person
Set up an automatic reply for information that rarely changes, such as hours, directions, and what to bring. A useful example is: “We check messages on weekdays from 10 a.m. to 5 p.m. We may reply more slowly during class and will get back to you by the next business day.” Adjust the hours and promise to match how you actually work.
Availability, a confirmed reservation, a refund, a damaged item, and a complaint need someone to check the details. “We received your request” is different from “Your booking is confirmed.” If a request has arrived but no one has checked the seats yet, say: “We’ll check availability and message you to confirm.” Send the confirmation only after a person has checked.
Walk through a Saturday class inquiry
Imagine someone comments on a pottery class post: “Can two people come Saturday? I left my phone number here.” Reply publicly: “Thanks for asking. Please message us through the contact link on our profile and we’ll check availability. We’ll remove the phone number from this public comment so it isn’t visible to others.” Do not copy the number into another post or a general list. Ask only for the information needed to handle the booking, in the private channel.
After checking the schedule, you might write privately: “We have two places at 2 p.m. Saturday. If you’d like them, send the booking name here. We’ll confirm once we’ve matched it to the class list.” If the customer says “Book us,” check the request against the available seats before calling it confirmed.
Now imagine a customer comments after class, “My bowl cracked in the kiln.” Acknowledge the problem without asking them to post order details publicly: “I’m sorry that happened. Please message us with the class date through the profile contact link so we can look into it. Please don’t post your name or phone number here.” Continue the conversation in private.
Handle spam and rights concerns separately
If the same advertisement keeps appearing, use the platform’s reporting, hiding, or blocking tools instead of arguing in the thread. Each platform’s controls work differently, so check what a setting actually blocks and decide what you want to remove or limit.
If a comment exposes someone else’s phone number or image, or appears abusive or infringing, avoid reposting it or starting a public argument. Keep only the record needed to handle the issue and use the platform’s reporting or support process. A public reply like “I just called you” can reveal that you contacted a particular customer; keep follow-up details in the private channel.
Before publishing, write down three things: which questions are fine to answer publicly, where reservations go, and who checks that channel and when. For example: “Directions and supplies in comments; bookings through Talk; checked by the owner by 5 p.m. on weekdays.” With that simple routine, both customers and anyone helping with the post know what to do next.
FAQ
Frequently asked questions
May we take a phone in comments?
Keep names and phone numbers out of public replies. Remove or hide the comment where possible, then point the customer to your private contact channel.
How do we stop spam?
Use the platform’s reporting, hiding, or blocking tools. Check what each setting actually limits.
Several windows?
Choose one main booking channel. If a team replies, assign an owner and keep availability in one shared place.
An infringing comment?
Keep only the record needed to handle it, then use the platform’s reporting or support process instead of reposting or arguing publicly.
Is automation enough?
It works for fixed details like hours and directions. A person should confirm bookings and handle refunds, damage, or complaints.
Related updates
What to Put in the First Paragraph of a Naver Blog Post
A practical Naver blog writing example for a pottery class: explain the offer, disclose gifts or payment, and make booking details clear.
Read moreBlogChoose Your Blog Photos Before You Upload
A practical guide to planning a few clear blog photos, choosing a representative image, and checking the post on your phone, with a pottery class as an example.
Read moreBlogWhat to Prepare Before You Commission a Blog Post
A practical pottery-class example shows what to tell a blog writer: who the post is for, accurate class details, approved photos, and clear sponsorship disclosure.
Read more