CRM & Automation

One connected record for the relationship.

Your website, inquiry channels, booking, pipeline, and approved assistant workflows should not operate as separate systems. PGT configures CRM & Automation so the contact, conversation, attribution, booking, and opportunity remain connected.

What it does

What the connected CRM supports

01

Contact and opportunity records

Keep approved contact facts, conversation history, attribution, stage, and next action together.

02

Unified Inbox

Bring supported channels into a shared working view so the team can see context before responding.

03

Booking and follow-up

Connect calendar actions, confirmations, reminders, rescheduling, and approved follow-up to the same record.

04

Pipeline visibility

Show active opportunities, ownership, stage, and required next steps without relying on memory.

05

Workflow automation

Trigger approved actions from clear events while respecting consent, suppression, escalation, and stop conditions.

06

Reporting

Connect source, engagement, booking, and opportunity activity so the practice can evaluate the system with real data.

Connected delivery

The public lead and sales record

The configured CRM owns the front-office context required to move an inquiry forward.

  • Contact forms and strategy-call bookings
  • Supported chat, call, SMS, and Reception AI inquiries
  • Source and campaign attribution
  • Contacts and opportunities
  • Pipeline stages and sales activity
  • Approved nurture, follow-up, booking, proposal, and close automation
How it connects

Done-for-you configuration

PGT maps the fields, stages, forms, calendar, workflows, permissions, and integrations included in the engagement. The practice receives a configured operating layer rather than an empty account and a generic template.

The website can launch before every final nurture workflow is complete. Replaceable embeds and actions allow working destinations to be inserted without redesign.

Frequently asked questions

Clear answers before the next step.

Does the website have to wait for every workflow?

No. Launch requires working contact and booking destinations, while replaceable configuration allows nurture and automation details to continue without holding up the site architecture.

Does the CRM replace professional systems of record?

Not by default. The strategy call and implementation scope identify what connects, what remains separate, and where professional or sensitive records must stay.

Your next step

Connect the journey from inquiry to decision.

Start with the breakdown that matters most. We will map the right first step and how it connects to the wider system.