Multilingual public page
The store decides whether to expose a public customer page.
Show services in Korean, English, Japanese and Chinese and handle email-first booking requests in the existing reservation workflow.

DM inquiry → translation → schedule check → customer details kept separately
Multilingual service page → booking request → existing bookings → existing customer record
The customer booking flow is shown in English, and international requests still enter the existing booking workflow.


The store decides whether to expose a public customer page.
A customer without a Korean phone number can start a request on the multilingual page.
The store reviews the request in the existing booking flow; it is not treated as instant confirmation.
Domestic and international customers stay in one customer list.
Apply for beta
Review fit with your current workflow
Guide setup and customer-data migration scope
Use the beta and share feedback
Yes. The public customer page can receive email-first requests without requiring a Korean phone number.
Customer pages support Korean, English, Japanese and Simplified Chinese.
No. International requests stay inside the existing booking and customer workflow.
No. The store reviews the request; instant confirmation is not currently supported.
International card payments are not currently supported.
No. It appears only when the store explicitly enables the public page.
Start with your business type, name and email. Add operational details only if they are useful.