Hey Alin awesome idea. I’ve built DFY “business-in-a-box” membership flows in GoHighLevel for affiliates and creators. Quick wins: use GHL Memberships for gated content, Stripe/PayPal for payments, automated onboarding funnels (welcome + first-task), and a simple trial sticky retention flow. If you want, I can share a one-page 24-hour build checklist you can copy. Olly (GHL / CRM specialist)

Hi @Duncan Riley you wellcome to this group

Nice — below are three ready-to-paste replies (short public, helpful public with one practical tip, and a DM/offer you can send to take the work off their hands). All are professional, non-salesy, and position you as the person who can get DBR running and scale it later.

@Ben Tracey Great question — I usually recommend provisioning a new GHL number for immediate use, then porting the client’s existing number later if brand continuity is important. Porting can be slow and sometimes causes downtime, so a temporary number keeps SMS flowing while you handle the paperwork. If you want, I can take care of the porting + GHL configuration for you (audit, port request, test deliverability)

Hi @Kevin Utermann , thanks for the clear write-up and sorry you’re running into this, that’s frustrating... From what you describe it’s usually one of a few things: (1) the system-generated contract email is being blocked at the transactional-email layer (wrong sender, broken SMTP/SendGrid-like connection, or bounces/suppression) (2) the specific contract email template or “send via system” toggle isn’t active/assigned (3) the recipient address is marked opted-out/suppressed, or the final-PDF routine is tied to a webhook/automation that isn’t firing after the last signature Quick practical checks you can run now: Try to confirm the Payments → Contracts email template is active and assigned to that contract type; verify the system sender / transactional email provider is connected and showing no bounces; check the contact record for opt-outs; test with a fresh contract sent to a different inbox while watching the activity/audit logs for send errors; and inspect any automation/webhook that handles “on signed” events (that’s often where PDF generation is triggered) As a short-term workaround you can continue sending the contract link manually or create a lightweight workflow that emails the signed PDF when the “signed” event appears If you want, I can dig in and audit templates, logs and automations for you — send screenshots or temporary access and I’ll trace the send path and the PDF-generation flow Let me know what you find regardless