Florist CRM
At a florist the person who places the order and the person who receives the flowers are not the same. When the two are squeezed into a single record, the delivery address, the card message and next year's anniversary are lost together; the mistake is only discovered at the delivery door.
The sender is a customer record and the recipient's name and address are fields on the order; in Rapitek CRM the delivery time window and the second attempt run from that same order record.
- Keep the sending customer and the delivery recipient apart; write the card message into the order's field and, for anonymous sending, leave the sender's name out of the card text
- Write the delivery time window onto the order; have the courier close the delivery from the mobile app with location verification, have the person taking delivery sign on the signature screen, and open a second attempt task when the recipient cannot be found
- Put work that must close the same day, such as funeral wreaths and ceremony orders, into a separate queue, set its owner with the assignment rule you define during setup, and notify the team as the status changes
- Run the pre-order window before a special day with stepped follow-up tasks; turn the lists from hotel, office and agency accounts into quotes at their own agreed prices
| Separating Sender and Recipient | The sender is a customer record; the recipient's name, address and phone number sit in the order's own fields. When the recipient later places an order of their own they become a separate customer record, so the two histories do not get mixed up. |
|---|---|
| Card Message and Anonymous Sending | The card text is a field on the order and passes to the delivery task along with the address; when the sender wants to stay anonymous their name is not written into the card text and stays only on the order record. |
| Narrow Delivery Window and Second Attempt | An order carries a time window, not just a day; the courier closes the delivery with location verification and the person taking delivery signs on the signature screen in the mobile app. If the recipient is not at the door the outcome is recorded on the task, and the time for the second attempt is agreed with the recipient from the shared WhatsApp or SMS inbox. |
| Corporate Pre-Order Window | Hotels, offices and agencies give their lists weeks before a special day; that list is opened as a pre-order under the account, turns into a quote at the price defined for that account, and is split into individual tasks on the delivery day. |
A flower order concerns two people at once: the one who pays and the one who opens the door. When both are written on the same line of an order taken over the phone, by the time the same anniversary comes round the following year who sent what to whom can no longer be read. On days like Valentine's Day or Mother's Day the number of orders multiplies while the delivery window narrows; the text of the card message, what to do if nobody is found at the door and when the arrangement needs to be made up all sit in three separate places.
In Rapitek CRM the sender is a customer record while the recipient is the order's own address field; because the two are kept apart, next year's reminder can be built on last year's order. The delivery time window is written on the order; the courier closes the delivery from the mobile app with location verification, and the person taking delivery signs on the signature screen in the same app. If nobody is at the door the outcome is recorded on the task, and a new time for the second attempt is agreed with the recipient over WhatsApp or SMS. Work that has to close the same day, such as a funeral wreath, waits in a separate queue, and the assignment rule defined during setup determines its owner. Corporate lists that come in before a special day are opened as pre-orders and split into individual tasks on the delivery day.
The scope of the plans and the items priced separately are set out on the pricing page.
