Kajikaji Successfully Reduces Reservation Handling Workload by More Than Half with "Rocaopu" Introduction
Kajikaji, an order cake shop, announced a case study where they reduced reservation handling workload by more than half after introducing "Rocaopu." The system streamlines complex LINE-based reservation processes through Google Business Profile operation support, making operations more efficient and alleviating burdens during peak seasons.
📋 Article Processing Timeline
- 📰 Published: April 3, 2026 at 20:00
- 🔍 Collected: April 3, 2026 at 11:30
- 🤖 AI Analyzed: April 21, 2026 at 05:36 (426h 5m after Collected)
Rocaopu Inc. (Headquarters: Shinjuku, Shinjuku-ku, Tokyo; Representative Director: Masataka Agata; hereinafter: Rocaopu) is pleased to announce a case study where "Kajikaji," a confectionery store specializing in custom order cakes, introduced "Rocaopu," a comprehensive support system for Google Business Profile (Google Maps) operation, survey utilization, and review promotion, and successfully reduced its reservation handling workload by more than half.
## Background of Rocaopu Introduction
### Increased Burden of Reservation Handling Due to Rising Orders; Systematization of Front-end Operations Became Urgent
Kajikaji adopts a style of creating custom order cakes by carefully listening to each customer's requests. For this reason, they have primarily accepted orders through LINE instead of by phone.
However, with the increase in the number of orders, interactions such as "listening to requests," "adjusting pick-up dates and times," and "confirming details" increased. The time spent per customer interaction became longer, and with multiple orders proceeding simultaneously, responses and confirmation tasks tended to accumulate.
Especially during peak seasons, reservations concentrated, and the front-end operations alone consumed significant time, leading to situations where "I couldn't handle it by myself." This impacted original tasks like manufacturing and preparation, revealing operational challenges.
Against this backdrop, Rocaopu was introduced to streamline the process of receiving necessary information at the time of reservation and alleviate the burden of interactions.
By being able to acquire necessary information in advance through the reservation form, the back-and-forth communication decreased. Information became organized at the initial stage of interaction, leading to improved overall operational efficiency.
### < Challenges Before Introduction >
- Increased time for confirmation, adjustment, and content confirmation via LINE due to rising orders.
- Situations where "I couldn't handle it by myself" due to time consumed by front-end operations.
- Difficulty in handling other tasks due to overlapping reservation responses.
- Reservation handling was particularly burdensome during peak seasons (e.g., Christmas).
### < Results After Introduction >
- Transition from being overwhelmed to operating with more leeway.
- Reservation handling workload reduced by more than half.
- Reduced time for confirmation and adjustment, leading to more time for other work.
- Escaped from the state of "being constantly overwhelmed."
## Background of Rocaopu Introduction
### Increased Burden of Reservation Handling Due to Rising Orders; Systematization of Front-end Operations Became Urgent
Kajikaji adopts a style of creating custom order cakes by carefully listening to each customer's requests. For this reason, they have primarily accepted orders through LINE instead of by phone.
However, with the increase in the number of orders, interactions such as "listening to requests," "adjusting pick-up dates and times," and "confirming details" increased. The time spent per customer interaction became longer, and with multiple orders proceeding simultaneously, responses and confirmation tasks tended to accumulate.
Especially during peak seasons, reservations concentrated, and the front-end operations alone consumed significant time, leading to situations where "I couldn't handle it by myself." This impacted original tasks like manufacturing and preparation, revealing operational challenges.
Against this backdrop, Rocaopu was introduced to streamline the process of receiving necessary information at the time of reservation and alleviate the burden of interactions.
By being able to acquire necessary information in advance through the reservation form, the back-and-forth communication decreased. Information became organized at the initial stage of interaction, leading to improved overall operational efficiency.
### < Challenges Before Introduction >
- Increased time for confirmation, adjustment, and content confirmation via LINE due to rising orders.
- Situations where "I couldn't handle it by myself" due to time consumed by front-end operations.
- Difficulty in handling other tasks due to overlapping reservation responses.
- Reservation handling was particularly burdensome during peak seasons (e.g., Christmas).
### < Results After Introduction >
- Transition from being overwhelmed to operating with more leeway.
- Reservation handling workload reduced by more than half.
- Reduced time for confirmation and adjustment, leading to more time for other work.
- Escaped from the state of "being constantly overwhelmed."