CRM Consultant, Philippines

How Philippine companies win customers, route by route

A CRM design starts with how the business actually wins customers, and in the Philippines that differs a great deal by sector.

• Real estate developers sell through in-house sellers and networks of brokers and their agents. Each buyer passes through inquiry, site tripping, reservation, document submission and loan or payment arrangements, and every step has an owner.
• Distributors and consumer goods suppliers serve retailers and dealers across provinces, where the important view is reorder frequency and coverage by area rather than a classic pipeline.
• Business service firms, including IT and professional services, run longer consultative deals with proposals, revisions and client approvals.
• Schools, clinics and other service providers handle high volumes of inquiries that must be answered quickly before the prospect moves on.

For each route, I document where inquiries come from, who responds, what has to happen before a sale is real and what finance needs at the end. That produces a short set of pipelines, where a deal only advances when the buyer acts, for example by submitting documents or paying a reservation fee, not when a seller feels confident.

Shared accounts and contacts sit across all of them, so a buyer who inquires twice through different brokers is recognized as the same person. The method follows my CRM consulting approach, applied to Philippine sales structures.

Chat, social and calls: getting inquiries into one queue

Many Philippine companies receive most of their inquiries through chat apps and social media pages. Those channels are fast and familiar for buyers, but they scatter leads across personal accounts and shared logins, and nobody can tell how many inquiries went unanswered last week.

The CRM design covers three things. First, capture: which channels can be connected to the CRM directly, which need a connector, and which will rely on a quick manual entry by the person who received the message. I compare options on cost, reliability and how much each depends on a single platform's rules. Second, assignment: inquiries are routed by island, region, branch, product or language preference, with a clear owner and an escalation if nobody responds within the agreed time. Third, identity: since many inquiries arrive with only a name and a mobile number, matching rules use the number and email to recognize returning prospects.

Source tracking matters here too. When every lead carries its channel and campaign, you can compare social, search, referral and broker channels on closed sales rather than on message counts, which is where CRM design meets paid marketing and lead generation. Without it, marketing budgets follow whichever channel looks busiest, which is rarely the one that produces revenue.

Data Privacy Act consent, access and retention

The Data Privacy Act sets rules for how personal information is collected, used, shared and kept, and the National Privacy Commission issues guidance on applying them. A CRM holds exactly that kind of information, often for prospects who never become customers, so its design matters.

The CRM design I prepare usually provides for:

• the source and purpose of each contact, recorded when it is captured
• consent fields where consent is the basis, with the wording and date of what the person agreed to
• a clear process for withdrawal and for requests to access or correct data, reflected in every connected tool
• role-based access so brokers, dealers and branches see only their own prospects
• retention rules so stale leads are reviewed and removed rather than kept indefinitely
• an export log, since lead lists are easy to copy and hard to recall

Chat conversations raise a specific question: a friendly reply on a messaging app is not necessarily a recorded consent for marketing. Your counsel or data protection officer decides what counts, and whether registration or other obligations with the Commission apply to your organization. I also ask CRM vendors where data is hosted, because transfers outside the country carry their own considerations. My part is building a system that records and enforces whatever your advisors decide.

When a deal closes: passing data to BIR-ready billing

In the Philippines, invoices are issued from an accounting system that is subject to BIR rules, and many companies have registered that system as a computerized accounting system. The CRM should not compete with it. A quotation or proforma generated by the CRM must never be mistaken for a sales invoice, so I recommend document titles, numbering and wording that keep them clearly separate, checked by your accountant.

The handoff design answers practical questions with sales and finance together:

• which customer details are collected before a deal can close, including registered name, TIN, business style and address
• who creates the customer in the accounting system, and how the two records stay linked
• how VAT or other taxes appear on quotations, so buyers see the same figures later
• how withholding tax deducted by corporate customers is reflected, so collections match expectations
• which delivery, invoice and payment statuses come back to the CRM

Branch invoice series, books of accounts and tax treatment belong in the registered accounting system and with your accountant. The CRM's job is to hand over complete, approved orders. The systems side of these links, including bank and payment channels, is what I cover as an integration consultant for Philippine businesses.

Choosing a CRM and making adoption stick in the Philippines

I compare CRM options against the design we write together, not against vendor brochures. The shortlist might include Zoho CRM, HubSpot, Salesforce, Odoo CRM if Odoo is the likely ERP, or the sales features of a system you already own.

Philippine criteria often include how well the mobile app works for sellers who live on their phones and move between areas with uneven signal, chat channel integration, whether brokers and dealers can be given limited access at a sensible cost, how the CRM passes orders to your registered accounting system, local implementer support and where data is hosted.

Adoption is designed alongside the configuration. Sellers are measured on speed of response and conversion, so the CRM should make those easier, not add paperwork. I keep required fields to the minimum, automate reminders and handoffs, and set up the dashboards that sales heads review weekly: inquiries by source, response times, pipeline by stage and conversions by broker or branch. Rollout starts with one branch or team, and the setup is refined before others join.

All work is remote, scheduled in hours that overlap with Philippine business days. For other support, see the Philippines hub and my ERP consulting work in the Philippines.