
Customer relationship management starts with knowing who you are speaking to, what they need and what should happen next. A large spreadsheet is not enough if the same person appears several times, their preferences are unclear or nobody knows the latest stage of the relationship.
For Nigerian businesses and organisations, Yournotify brings contacts, lists, segments and messaging into a connected workflow. This guide focuses on the foundation: useful customer data, consistent updates and audiences that help your team communicate more effectively.
The same approach works for customers, members, applicants, subscribers and other people your organisation serves.
Table of Contents
A brand example: Starbucks and relevant member experiences
Starbucks’ announcement of its US Rewards programme describes membership levels and increasingly personalised benefits. The useful CRM lesson is that an established member and a new member do not always need the same experience.
A Nigerian restaurant, retailer or membership organisation can apply that principle at a simpler scale. Store the attributes you can maintain accurately, such as membership stage, preferred branch and recorded interests. Use them to decide who receives a welcome message, an appropriate offer or a service update.
The value comes from using reliable data to make communication relevant. A complicated profile with outdated fields will not help your team choose the right message.
Customer data priorities by industry
| Industry | Useful attributes | Example segment |
|---|---|---|
| Retail and hospitality | Preferred branch, interest and relationship stage | Customers interested in an eligible branch offer |
| Education | Programme, intake and application stage | Applicants who still need to complete a step |
| Automotive and property | Product interest, location and enquiry stage | Qualified enquiries awaiting an appointment |
| Professional services | Company, service interest and next agreed action | Enquiries ready for a consultation |
| Churches, associations and nonprofits | Membership group, location and communication preferences | Members who requested updates for a particular programme |
Keep audiences tied to their purpose. A service reminder and a promotional offer may use the same contact record but different eligibility rules. Maintain the person’s preferences alongside the information your team uses to target the message.
Worked example: one person, two different needs
Imagine a customer who first asks about a product and later books a service appointment. Their contact identity stays the same, but their stage and immediate need change. Update the relevant attributes and record the new activity rather than creating a second person in the database.
In Yournotify, keep the person in the appropriate operational list and use supported segment conditions to identify the current audience. A confirmed customer should receive appointment preparation, while someone still making an enquiry may need product information.
Before launching a campaign, review five matching contacts with the team responsible for follow-up. Ask whether the proposed message makes sense for each person. This simple quality check often reveals missing fields, stale stages or an overly broad segment.
Step 1: decide which information supports an action
Do not begin by collecting every possible detail. Start with the decisions your team needs to make. A training provider may need course interest, preferred location and registration stage. A retailer may need product interest, loyalty tier and communication preferences.
Create a small data dictionary before importing records:
| Field | Example | What it helps your team do |
|---|---|---|
| Name | Zaynab Example | Address the person clearly |
| Email or telephone | Verified contact detail | Use the appropriate communication channel |
city | Lagos | Share relevant location information |
interest | Weekend training | Select a useful offer or update |
lead_stage | Enquiry | Choose the next follow-up |
source | Website form | Understand where the relationship began |
Use stable field names and agreed values. If one import uses Lagos, another uses lagos_state and a third uses LAG, your filters will need extra work before they are reliable.
Step 2: clean and import a manageable sample
Open Contacts and review the available import workflow. Map names, email addresses and telephone numbers to their correct fields, then map useful extra columns to contact attributes.
Normalise telephone numbers into international format, remove empty or invalid records and review likely duplicates. Preserve the source of the data and the communication preferences your team needs. Membership of a contact list should not be treated as proof of permission for every message.
Import a small sample first. Check several profiles, including one with missing optional data and one with a longer name. Confirm that attributes appear under the intended keys before importing the full file.
Give the destination list a useful name, such as November workshop enquiries, rather than New list 7. A clear name helps someone else understand the audience later.
Step 3: use lists and segments for different jobs
A list is a stable grouping of contacts. A segment evaluates conditions to identify people who currently match a rule. Use lists for organised destinations and segments for decisions that should reflect changing data.
For example, keep everyone who requested course information in a Course enquiries list. Then create segments for location, interest or enquiry stage using the conditions available in your account.
| Audience need | Suggested approach |
|---|---|
| People imported from a particular event | A named list |
| Contacts currently at the enquiry stage | A segment based on the agreed stage attribute |
| People interested in a particular service | A segment based on the interest attribute |
| A review of one partner’s referrals | A list or segment using a consistently stored partner reference |
Preview the matched contacts before using a segment. Check someone who should match and someone who should not. If the result is surprising, inspect the underlying values rather than adding more filters blindly.
Step 4: keep records current through the API
For a custom application, create a contact through the Contacts API and store the returned identifier. The example below uses demonstration details; replace the list ID with a list from your workspace.
curl -X POST 'https://api.yournotify.com/contacts' \
-H "Authorization: Bearer $YOURNOTIFY_API_KEY" \
-H 'Content-Type: application/json' \
--data '{
"name": "Zaynab Example",
"email": "zaynab@example.com",
"lists": [12345],
"attribs": {
"city": "Lagos",
"interest": "weekend_training",
"lead_stage": "enquiry",
"source": "website_form"
}
}'
This request writes a contact to the chosen workspace. Test with demonstration data and keep the bearer key on your server. For later changes, use PUT /contacts/{id} with the supported fields rather than creating another contact every time someone changes their profile.
Where your application also tracks behaviour, use /sdk/identify with a stable external_id and integration namespace. This connects the application identity with the contact journey. Follow the current contact and identity documentation when implementing matching and updates.
Agree which system owns each field. Your booking system may own registration status, while your team maintains service interest. Two systems repeatedly overwriting each other will make even a carefully designed segment unreliable.
Step 5: turn better data into a better message
Start with a segment small enough to review. For example: contacts whose interest is weekend training and whose current stage is enquiry.
A useful email could say:
You asked about our weekend training programme. The next session is now open, and you can review the schedule and choose a suitable date here: https://example.com/training
The message explains why it is relevant and provides one action. When someone registers, update the stage and move their communication towards preparation and attendance rather than continuing enquiry reminders.
Use Yournotify Email, SMS or another suitable channel based on the message and the person’s preferences. Keep fallback wording for optional personalisation fields so missing data does not produce an awkward greeting.
Step 6: give the data a regular owner
Assign someone to review data quality and the most important segments. A practical weekly routine is to check new imports, investigate duplicate patterns, review failed contact updates and confirm that key stages still mean the same thing to everyone.
Track a few useful indicators:
- Percentage of contacts with a usable channel for the intended journey.
- Duplicate records found and resolved.
- Percentage with a known source and relevant stage.
- Enquiries progressing to the next agreed stage.
- Delivery failures or opt-outs that need attention.
These measures show whether your database is becoming more useful, not just larger.
Frequently asked questions
Should I create a new list for every campaign? Not always. Reuse a well-defined list where appropriate and use segments for changing conditions. Avoid making repeated copies of the same audience without a clear purpose.
Can I store information specific to my organisation? Yes. Use contact attributes with consistent keys and values, then use supported conditions to build relevant audiences.
What is the best first CRM improvement? Choose one contact source, clean its key fields and connect it to one useful follow-up. A small, accurate workflow is easier to expand than a large, inconsistent database.
Organise one audience this week
Open Yournotify Contacts, review a sample of your records and agree the fields your team actually uses. Build one list, one relevant segment and one follow-up that reflects the person’s current needs. Explore contact-list management as the foundation for more useful customer relationships.