This is a template that should be used to document each feature. It’s meant to be easy, not prescriptive - change it at will!
Table of contents
Definition
Status | NOT STARTED |
RBIberia Owner | |
RBI Owner |
Requirements
Problem statement
Correct communication for each scenario of the paused service
Avoid losing sales redirecting users to other services or offering other solutions such as discount codes
Acceptance criteria
Customized communication for each scenario related to the paused service
It could show extra content such as “discount code” communication specific for one or more scenarios
The goal of having a discount code is to avoid losing sale
Reduced area should be communicated in a proper way
In any case, in case of pick-up service active, it should be added a button to send the user to this type of service to avoid losing the sale
Reduced area with backup should be validated if it’s the same as “Master restaurant” feature
Success metrics / Data & Events
🤔 Assumptions
The solution should be agnostic and indipendent from the DMP used
The solution should be generic for all the markets
Solution
Scenarios
Note: these are high-level scenarios that must pass testing before we can release the feature. They should also be used to drive design. Note that we do not specify user interface details in these steps - that is deliberate so that we focus on the process and not on the UI since the UI can change throughout design and development.
Scenario 1: xxx
Steps | Expected results (example text) |
|---|---|
Weather | Es climatológicamente imposible llevar tu pedido como quisiéramos. Sentimos no poder atender ahora a tu hambre. Intentaremos restablecer servicio en los próximos 10 minutos. Atentamente, BURGER KING®Atención al cliente. |
No driver available | No hay disponibilidad para llevar a tiempo tu pedido. Sentimos no poder atender ahora a tu hambre.Te avisaremos cuando el servicio se restablezca. Atentamente, BURGER KING®Atención al cliente. |
Street closed | Estás geolocalizado en un área de reparto cortada. Nos es imposible llevar tu pedido como quisiéramos. Sentimos no poder atender a tu hambre. Te avisaremos cuando el servicio se restablezca. Atentamente, BURGER KING®Atención al cliente. |
Volume of orders | Demasiados pedidos en la parrilla. Ahora no podemos llevar tu pedido como quisiéramos. Sentimos no poder atender ahora a tu hambre. Intentaremos restablecer servicio en los próximos 10 minutos. Atentamente, BURGER KING®Atención al cliente. |
Technical issues | Un fallo técnico no nos permite llevar tu pedido como quisiéramos. Sentimos no poder atender ahora a tu hambre. Intentaremos restablecer servicio en los próximos 10 minutos. Atentamente, BURGER KING®Atención al cliente. |
Restaurant schedule | Hemos apagado la parrilla. Mañana la volvemos a encender. Sentimos no poder atender ahora a tu hambre. Te avisaremos cuando el servicio se restablezca. Atentamente, BURGER KING®Atención al cliente. |
Reduced area |
EXCLUDED:
Fallo conexión a internet. -> Un fallo técnico no nos permite llevar tu pedido como quisiéramos. Sentimos no poder atender ahora a tu hambre. Intentaremos restablecer servicio en los próximos 10 minutos. Atentamente, BURGER KING®Atención al cliente.
Design
Figma design here: [insert link]
Development
Check the dependency with Homeria to understand if it’s needed an effort on their side
0 Comments