- Your own account of missed enquiries
- Examples of enquiries that were missed or answered late, even from memory, show where setup should start. Buyer names are not needed. Without any examples the work begins from assumptions, and the first routes tested may not be the ones that leak.
- Logins to the enquiry channels
- To test routes, GullySales needs view access to the website form inbox, marketplace account, WhatsApp business number and call logs where they exist. Read-only is acceptable. A route we cannot see is left out of the setup and named as untested.
- Named people for replies and cover
- Each route needs one person who replies and one who covers absence, and both must agree. Without named people the templates have no sender and the sheet has no owners, so the setup runs but nothing moves.
- Approved wording for replies
- Someone with authority reviews the reply templates, including what staff may say about price, availability and delivery. Without that approval, templates stay as drafts and staff improvise, which defeats the purpose of a consistent first answer.
- A folder of quotations already sent
- The quotation register starts from what is already out. A folder of sent quotations, or an inbox search, is enough. Missing history is acceptable and is recorded as missing; the register then begins with the first new quotation.