By Touchbase Technologies · Published 2026-11-05

Keep customer and investor contact lists separate

A customer introduction and a fundraising update ask for different things. Keep those relationships separate when you organize contacts, choose templates and review recipients. A person's email address identifies a contact; it does not explain why they should receive a particular message. Use relationship labels and a campaign purpose together rather than sending to everyone in one combined address book.

This guide covers a practical contact structure for a small founder-led team. The field names and review procedure are a suggested worksheet, not a claim that every field is automatically available in Touchbase or your CRM. The fictional examples demonstrate decisions you should make before a campaign leaves your mailbox.

An original contact-routing illustration showing one contact record linked to separate customer and investor audiences, with an exclusion check before either campaign sends.

Start with the relationship, not the source file

A file named conference-contacts.csv tells you where a record came from. It does not tell you whether the person is a potential customer, an investor, a partner or someone who has asked not to hear from you. Keep the source, but do not use it as the sole audience definition.

For each contact, record the relationship relevant to your business, its supporting context and the next intended interaction. “Customer prospect: asked about our scheduling product at a demo” is different from “Investor prospect: public investment focus appears relevant.” Neither label should become a blanket authorization to send every future message.

Avoid turning all investors into customer prospects because both groups work at companies. Likewise, a paying customer is not automatically interested in your fundraising round. Your product demo, onboarding instructions and investor deck should each reach an audience selected for that purpose.

Use one identity with more than one relationship when needed

Some people have two legitimate relationships with your business. A founder might use your product and also invest personally. Duplicating their contact record for each role makes it easier to overwrite details, lose context or send the same campaign twice. Where your tools support it, keep a stable identity and attach the separate relationships to that record.

HubSpot documents that it automatically deduplicates contacts using email addresses and companies using domain names, with additional import options such as Record ID. That is useful identity handling, but identity matching does not decide campaign relevance. An import can match the right person while still putting them into the wrong audience.

Review the destination tool's rules before importing updates. Do not assume an integration preserves every label, subscription preference or relationship note unless you have checked the mapping. The CRM handoff worksheet explains how to define an explicit destination for researched leads.

A small worksheet for campaign eligibility

Field	Example	Why it matters
Contact identity	Stable CRM record or reviewed email	Avoid creating a new person for each file
Relationship	Customer prospect; investor prospect	Choose the appropriate conversation
Context	Requested a product walkthrough	Support the reason for this message
Campaign purpose	Invite to scheduling-product demo	State exactly what recipients will receive
Exclusion status	Unsubscribed, refused, invalid address	Keep ineligible contacts out
Owner and review date	Founder; reviewed November 5	Make approval accountable

Keep identity, relationship and exclusion as separate concepts. Removing a customer label should not erase an unsubscribe. Updating an email address should not automatically reset the person's preferences. When the same recipient appears twice in a source list, review the conflict before choosing which record to retain.

Work through a fictional audience review

Imagine a founder preparing a product-demo campaign with ten saved contacts. Four are customer prospects who requested more information, three are investor prospects, two are existing customers and one has opted out. The founder initially selects all ten because they came from a single event spreadsheet.

The campaign's purpose is to show a new prospect how the product handles appointment changes. The four customer prospects are candidates for that invitation after their details and preferences are checked. The three investors belong in a separate fundraising review. The two existing customers might receive a feature announcement with a different introduction, or no message if it is irrelevant. The opted-out contact stays excluded.

The result is not a smaller version of the same mass email. It is a clearer plan: one prospect invitation, a possible customer update and a separate investor conversation. The numbers are illustrative. They show why the relationship review happens before writing the subject line or choosing a design.

Select the template after selecting the audience

A prospect template should explain the relevant problem and a useful next step. A customer update should acknowledge the existing relationship and explain what changed. An investor message may need a fundraising context and an appropriate deck. Mixing these purposes produces awkward messages even when the personalization fields render correctly.

Use a recipient preview before approval. Check the name, company where relevant, product, call to action and every shared link. If an investor deck appears in a customer campaign, stop and correct the audience or template. If a customer gets “Have you heard of us?”, check whether your prospect segment accidentally includes active users.

For recurring campaigns, save the audience definition alongside the template. “Customer prospects with a reviewed product fit, excluding refusals and unsubscribes” is more useful than “List 3.” A named owner should be able to explain who will enter the audience later and who will be removed.

Preserve exclusions across imports

Imports and signup webhooks can add new records and update existing ones. Treat an incoming record as data to reconcile, rather than an instruction to send a campaign immediately. Preserve the event or file source and inspect how it maps to the contact's existing relationship and preferences.

For example, an investor later signs up for your product. That event may justify adding a customer relationship or onboarding state. It does not mean their older fundraising correspondence should appear in a product announcement. Conversely, a new signup must not silently restore an address previously excluded from promotional mail. Test your mapping with safe sample records before applying it to a real audience.

Put the structure to work in Touchbase

Touchbase separates customer and investor contacts so the audience can match the work you are doing. Review the company and product context, save relevant contacts into the appropriate group, and create a campaign for a defined purpose. Use the template preview during campaign creation and check recipients before enabling any automation.

Existing contacts and website signups can be brought into your workflow, with configured CRM connections available for lead handoffs. Check what your destination actually receives; do not assume a complete two-way CRM synchronization. See the signup contact-sync checklist for a more detailed import review and the pricing page for current sending allowances.

Make the final check easy to repeat

Before approving a campaign, write a one-sentence audience rule and read five sample records against it. Inspect edge cases: a person with two relationships, an existing customer, a duplicate and an excluded address. If you cannot explain a recipient's inclusion, hold that record for review. Clear contact organization protects the purpose of the conversation and makes campaign results easier to interpret.

Prepared with AI assistance and checked against the sources linked in this guide.