A
?

Design4Space

Interior Design / Renovation← All clients

Full history

44 statements, 39 still standing. Ordered by when they were said, not when we read them.

  1. 2026-08-22 01:42WhatsAppcontext· event-lead-process

    Attendance for the 23 August Reno Expedition is tracked in dated tabs in the shared Google Sheet (e.g. "22 AUGUST 2026"); agency asked if D4S is tracking on a different sheet like last year

    D4S Reno Expedition Leads

  2. 2026-08-20 10:05WhatsAppdecision· unconfirmed-lead-assignment

    Unconfirmed leads to be assigned out to IDs from Thursday/Friday after the Wednesday-evening broadcast; on 20 Aug Alex confirmed assigning can start, with branches updating the sheet on any replies

    D4S Reno Expedition Leads

  3. 2026-08-20 10:05WhatsAppdecision· event-lead-handover

    Broadcasts and followups have been sent — leads can now start being assigned out to designers for them to try and contact as well.

    D4S Reno Expedition Leads

  4. 2026-08-20 10:05WhatsAppconstraint· lead-sheet-integrity

    If designers get replies or confirmations, kindly help to update the sheet so that statuses can be tallied up.

    D4S Reno Expedition Leads

  5. 2026-08-19 07:29WhatsAppcommitment· event-rsvp-timings-headsup

    D4S asked for a heads-up on finalised RSVP timings so they can arrange tables and chairs; Jun Kai committed to sending it over tomorrow.

    D4S Reno Expedition Leads

  6. 2026-08-19 07:21WhatsAppcommitment· event-rsvp-timings-headsup

    When RSVP timings are finalised we need a heads-up to arrange tables & chairs — agency to send over tomorrow

    D4S Reno Expedition Leads

  7. 2026-08-18 12:48WhatsAppdecision· unconfirmed-lead-assignment

    Broadcast to leads Wednesday evening; confirmations from it updated, then unconfirmed leads can be assigned out to IDs on Thursday and Friday, with our setter still calling alongside.

    D4S Reno Expedition Leads

  8. 2026-08-18 12:48WhatsAppdecision· unconfirmed-lead-assignment

    Non-confirmed leads can be assigned out to IDs from Thurs & Fri, after Wednesday evening's broadcast; setter will still be calling them alongside

    D4S Reno Expedition Leads

  9. 2026-08-18 12:34WhatsAppcommitment· booking-confirmation-format

    Agreed to add the Excel row number to every Booking Confirmation message so D4S can locate the corresponding row quickly.

    D4S Reno Expedition Leads

  10. 2026-08-18 12:34WhatsAppdecision· booking-confirmation-format

    Booking Confirmations will include the Excel row number so branches can locate the corresponding row quickly

    D4S Reno Expedition Leads

  11. 2026-08-18 12:34WhatsApprisk· duplicate-leads

    Recurring duplicate/misleading lead entries — same number appearing under different names (social media username overwrites), and leads signing up twice causing cross-branch assignment conflicts.

    D4S Reno Expedition Leads

  12. 2026-08-18 05:58WhatsApprisk· missing-leads-in-system

    A lead raised by Edmund could not be found in our system or Meta lead form submissions — possibly wrong name/number input; confirmation sent manually and situation being monitored.

    D4S Reno Expedition Leads

  13. 2026-08-17 13:04WhatsAppcomplaint· lead-sheet-integrity

    Lead sheet rows went misaligned — "Yesterday 50 leads haywire" — editing was paused, sheet reverted to a previous version, and statuses had to be manually patched.

    D4S Reno Expedition Leads

  14. 2026-08-17 02:15WhatsAppcomplaint· lead-sheet-integritysuperseded

    Around 50 leads went haywire in the sheet — rows were accidentally edited so entries and names were misaligned; sheet had to be reverted and editing paused

    The later WhatsApp message of 2026-08-17 13:04 restates the same lead-sheet misalignment incident more completely, adding the manual status patching, so it replaces the earlier 02:15 account of the same event rather than describing a new one.

    D4S Reno Expedition Leads

  15. 2026-08-14 03:11WhatsAppcontext· duplicate-leads

    Apparent duplicates are often the same lead — a social media username can overwrite the contact name when the phone number matches; separately some leads genuinely signed up twice and branches need to deconflict

    D4S Reno Expedition Leads

  16. 2026-08-14 03:11WhatsAppcontext· duplicate-leads

    Same number appearing under two names is not a duplicate — a social media username overwrites the contact when the lead also messages D4S on FB/IG

    D4S Reno Expedition Leads

  17. 2026-08-13 11:25WhatsApprisk· event-lead-handover

    We need to inform Jacqueline on the above, cos she has been the one doing the contact since day 1 and we all depend on her dissemination

    D4S Reno Expedition Leads

  18. 2026-08-13 11:00WhatsAppdecision· event-lead-process

    1) Leads received 2) telemarketing from Atlas Media contact & assign, put in the groupchat 3) Our ID will contact them

    D4S Reno Expedition Leads

  19. 2026-08-13 11:00WhatsAppdecision· event-lead-process

    Process: leads received → Atlas Media telemarketing contacts, confirms and posts assignment in the group chat → D4S ID contacts the lead and sets the appointment

    D4S Reno Expedition Leads

  20. 2026-08-13 09:26WhatsAppdecision· event-lead-process

    Process agreed: our side sends confirmation message + calls to chase, posts a confirmation alert into the group, requests floor plan and posts floor plan alerts; D4S side ensures a designer reaches out and sets the appointment.

    D4S Reno Expedition Leads

  21. 2026-08-11 10:20WhatsAppdecision· non-event-lead-ownership

    Leads from homematch/qanvast/ezid/direct email/WA/sixides/renonation/hometrust stay with D4S's own team — "these are our bread & butter, you need to follow up as normal". Handover applies to event leads only.

    D4S Reno Expedition Leads

  22. 2026-08-11 10:15WhatsAppdecision· event-lead-handover

    I will log u out from here as they have a better way of confirmation... u just follow up existing our existing leads

    D4S Reno Expedition Leads

  23. 2026-08-11 10:15WhatsAppdecision· event-lead-handover

    Agency takes over event lead follow-up; Jacqueline is logged out of the event lead system and only follows up existing event leads until Friday, updating the spreadsheet.

    D4S Reno Expedition Leads

  24. 2026-08-11 10:15WhatsAppcontext· lead-contact-method

    Previously Jacqueline led with text rather than calls — repeated META lead calls got her blocked/restricted; most confirmed appointments came via text. Agency says they call remotely from a landline with no ban issues, plus a confirmation button and automated floor plan collection

    D4S Reno Expedition Leads

  25. 2026-08-11 09:51WhatsAppcontext· lead-contact-method

    D4S's own experience: calling META leads multiple times gets them blocked and restricted, so they message first, call once or twice, and follow up by chat — most confirmed appointments come via text.

    D4S Reno Expedition Leads

  26. 2026-07-19 23:08WhatsAppdecision· unconfirmed-lead-assignment

    Notifications are back up; patched leads are marked "MANUAL" in the lead sheet, and new leads continue the same branch assignment as per the Google Sheet.

    Leads FB/IG D4S

  27. 2026-07-19 23:08WhatsAppdecision· missing-leads-in-system

    Notifications are back up; backlog notifications should be ignored, patched leads are marked "MANUAL" in the sheet, and branch assignment continues as per the same Google Sheet.

    Leads FB/IG D4S

  28. 2026-07-16 10:32WhatsApppreference· lead-contact-method

    Send fresh leads out as they come — "Don't wait to send together."

    Leads FB/IG D4S

  29. 2026-07-16 10:32WhatsAppcomplaint· missing-leads-in-system

    "Able to send out fresh leads? Don't wait to send together" — client pressing for fresh leads to be released as they come rather than batched.

    Leads FB/IG D4S

  30. 2026-07-16 10:32WhatsApppreference· event-lead-process

    "Able to send out fresh leads? Don't wait to send together" — wants fresh leads sent as they come rather than batched.

    Leads FB/IG D4S

  31. 2026-07-15 06:23WhatsApprisk· lead-sheet-integrity

    Root cause is a previously flagged issue — the API cannot match to the raw lead data from the D4S page; a fix is being tested on a new Google Sheet and they might need to start from that sheet instead.

    Leads FB/IG D4S

  32. 2026-07-14 05:09WhatsAppdecision· event-lead-process

    While the Google Sheet is down, D4S to input leads into their own Excel and disseminate to branches accordingly.

    Leads FB/IG D4S

  33. 2026-07-14 05:09WhatsAppdecision· unconfirmed-lead-assignmentsuperseded

    While the sheet is down, Design 4 Space to keep contacting every Meta lead, record them in their own excel and disseminate to branches accordingly — following the branch of the last lead in the sheet.

    The 20 Aug WhatsApp message from Alex sets out a new assignment routine — unconfirmed leads assigned to IDs Thursday/Friday after the Wednesday broadcast with branches updating the sheet — which replaces the 14 Jul interim workaround that applied only while the sheet was down.

    Leads FB/IG D4S

  34. 2026-07-14 05:09WhatsAppdecision· event-lead-handoversuperseded

    While the Google Sheet is down, input Meta leads into your own excel and disseminate to branches accordingly.

    The 11 Aug 2026 WhatsApp message ends the interim arrangement from 14 Jul 2026 by logging them out and limiting them to following up existing leads, since a better confirmation process now handles new ones.

    Leads FB/IG D4S

  35. 2026-07-11 07:00WhatsAppcommitment· missing-leads-in-systemsuperseded

    All leads after #520 will be patched into the sheet once the link issue is resolved.

    The 19 Jul WhatsApp message resolves the pending patch promised on 11 Jul, confirming the link issue is fixed and stating how patched leads are now marked, so it replaces the earlier interim instruction at equal authority.

    Leads FB/IG D4S

  36. 2026-07-11 06:58WhatsApprisk· missing-leads-in-systemsuperseded

    Google Sheet automation broke — last entry was #520 dated 5/7/26; leads stopped populating.

    The 19 Jul WhatsApp message reports the automation restored and patched leads marked "MANUAL", resolving the broken-feed state reported on 11 Jul at equal authority.

    Leads FB/IG D4S

  37. 2026-06-22 05:23WhatsApprisk· duplicate-leads

    A person (Jacqueline/Deon Chua) reports their identity has been misused to fill FB ad forms since 28 Nov 2025; two police reports made, and they ask not to be contacted and for it to be reported to Facebook.

    Leads FB/IG D4S

  38. 2026-06-22 05:23WhatsApprisk· lead-sheet-integrity

    A person (Deon Chua / Jacqueline's number) reports their identity is being misused to fill FB ad forms since 28 Nov 2025; two police reports made, and they ask not to be contacted again on future ads.

    Leads FB/IG D4S

  39. 2026-05-05 12:00WhatsAppcommitment· ad-creative-refresh

    New ads are in the midst of editing and will be out by end of week.

    Leads FB/IG D4S

  40. 2026-04-01 07:09WhatsAppcomplaint· duplicate-leads

    "This kind of scam leads, no need send in la…" — Richard on junk/scam form submissions being passed through.

    Leads FB/IG D4S

  41. 2026-03-20 07:13WhatsAppconstraint· lead-refund-policy

    Leads that don't reply or don't show up can't be refunded or replaced, since they come direct from Facebook and Instagram ads; the client should update lead status in the Google Sheet instead.

    Leads FB/IG D4S

  42. 2026-03-20 07:13WhatsAppconstraint· duplicate-leads

    Leads come direct from Facebook and Instagram ads, so no-replies or no-shows cannot be refunded or replaced.

    Leads FB/IG D4S

  43. 2026-03-19 08:06WhatsAppdecision· lead-sheet-integrity

    We've ported the data over to a new Google Sheet; that's the sheet to use going forward (link shared in chat).

    Leads FB/IG D4S

  44. 2026-03-19 08:06WhatsAppdecision· lead-sheet-integrity

    Data has been ported over to a new Google Sheet which the client team can access directly (edit access granted on request).

    Leads FB/IG D4S