Knowledge base
Learn the basics. Compare your options.
Understand AI automation, chatbots and CRM before choosing software or paying for help. Learn what each approach does, compare its costs and responsibilities, and use a practical checklist to decide what fits your work.
Start with the question you need to answer
Start here if you are exploring a topic, comparing software, reviewing a service proposal or deciding whether your current tools are enough. You can learn the concepts, build a shortlist and try a small evaluation before committing to a purchase.
- How should I compare software and implementation services?
- Which kind of solution fits the problem?
- What are the parts of an automated workflow?
- How does a message become a record and a next action?
- Which topic should I study next?
- Where should I look when something goes wrong?
- What do the common terms mean?
Choose the type of solution before comparing brands
A CRM, a chatbot and a service provider answer different needs. Define the problem first, then compare options in the same category. These are starting points to evaluate, not a universal ranking.
| Your question | Options worth comparing | What should decide the choice |
|---|---|---|
| Where should customer details and follow-up live? | A structured spreadsheet, a ready-made CRM or a custom system | Record relationships, team access, daily use and the work needed to maintain it |
| How should messages be answered? | Staff inbox, configured reply flow or knowledge-assisted chatbot with staff handover | Question variety, consequences of an incorrect answer and who handles exceptions |
| How should data move between tools? | Native features, workflow software or a custom connection | Supported actions, access rules, failed-run recovery and ongoing operating effort |
| Who should build and maintain the setup? | Your team, a specialist freelancer, an implementation company or an internal hire | Available skills, scope clarity, documentation, continuity and who owns each account |
| Should we change anything yet? | Improve the current process, run a small trial or invest in a wider build | A specific problem and evidence that the proposed change addresses it |
A service provider may configure software you pay for separately. Compare the software subscription and the implementation agreement as separate decisions.
Use the same problem to compare each option
Choose a small, representative example with dummy data. Use the same input and expected outcome for each candidate so that a polished demonstration does not replace an evaluation.
Write the must-have outcome
For example: a returning customer makes a new enquiry, the correct contact is reused, a separate opportunity is recorded and the responsible person sees the next task.
Compare evidence and gaps
Record what documentation supports, what your trial demonstrates and what is still unknown. Ask each provider to show the same normal case and failure case.
Count cost and responsibility
Include required plans, usage, setup time, support, data export and the person responsible for corrections. An inexpensive subscription can still take substantial staff time.
Keep a justified shortlist
Write why each option fits, where it is a poor fit and which question remains unresolved. Keeping the current tools is a reasonable result when they meet the requirement.
Five parts of an automated workflow
A tool is only one part of the process. Describe these parts in plain language before choosing a platform.
| Part | Meaning | Example to reason through |
|---|---|---|
| Trigger | An event that starts a workflow | A website enquiry arrives with a source reference |
| Information | The records and approved material the workflow can use | A contact record, service catalogue or current booking calendar |
| Rule or decision | A condition that determines the next permitted step | If a booking source is unavailable, record a request for staff review |
| Action | A defined operation, such as reading information, creating a task or updating a record | Look up an enquiry record, then create a task for the assigned staff member |
| Feedback and recovery | A record of the outcome and a way to deal with incomplete work | Keep a failed calendar check visible instead of calling the booking confirmed |
This is a general model. A selected platform may use different names or combine several parts in one component.
Follow one enquiry through the system
Illustrative example, not a client conversation or a completed system test. A customer asks about a service and a preferred appointment date.
Read the message and its context
Keep the channel, message reference and relevant conversation details. Do not treat a repeated delivery of the same event as a new customer request.
Find the approved information
Use the service information for general questions. A description of opening hours is not proof that a particular appointment is free.
Resolve uncertainty
Ask for a clear date or refer the question to staff if the request cannot be interpreted reliably. A fluent reply can still leave a necessary field unresolved.
Create or update the right record
Use an agreed matching rule to find the contact, then attach the enquiry or opportunity. Keep the original request separate from a confirmed booking.
Assign the next action
A named person or monitored queue receives the task, context and status. If a person takes over, define which automated replies stop and how they resume.
Check the result
A successful request to another tool does not by itself prove the intended business outcome. Read the resulting status or place incomplete work in a visible recovery queue.
Choose a learning path
Foundations
Understand automation
Read the AI automation introduction and small-business workflow guide. Learn to map a repeated process before adding tools.
Conversations
Understand chatbots and handover
Compare replies, connected actions and staff decisions on the business chatbot page. Follow the channel-specific explanation on Messenger chatbot workflows.
Records
Understand CRM
Start with CRM for small business, then study CRM automation. Learn how contacts, opportunities, activities and staff responsibilities fit together.
Architecture
Configure or build a system
Read the custom CRM explanation for data models, connected systems and maintenance decisions. The ERP introduction explains the different operational scope.
Economics
Understand the cost model
Use the pricing explanation to separate setup, subscriptions, activity and support. The Philippine automation-cost guide goes deeper into budgeting and assumptions.
Operations
Keep follow-up useful
Study lead follow-up automation to understand triggers, conversation state, ownership and stop rules. More messages are not the same as a useful next action.
Troubleshoot by layer
These are diagnostic questions, not a promise that one change fixes every platform. Change one part at a time and keep a record of the original condition.
| Symptom | Check first | What the check helps distinguish |
|---|---|---|
| The reply sounds correct but gives the wrong fact | Approved source, source date and what information was actually retrieved | An information problem versus a wording problem |
| The message is answered but no task appears | The action result, target account, field mapping and staff queue | A conversation response versus a completed system update |
| The same lead appears more than once | Event references, retry history and contact-matching rules | Repeated delivery versus genuinely separate enquiries |
| A person replies but automation keeps sending messages | Conversation state, running actions, pause scope and resume rules | Staff handover versus a separate workflow that is still eligible to run |
| A record exists but nobody follows up | Owner, next task, queue visibility and what happens when the owner is absent | Data storage versus operational responsibility |
| Costs rise while enquiry volume stays similar | The billing unit, workflow steps, repeated runs and additional channels | Customer volume versus billable activity |
A working glossary
| Term | Plain-language meaning |
|---|---|
| Workflow | A connected set of steps that turns an event and input into defined actions and an outcome |
| Knowledge source | Approved material or records used to answer a question; it still needs ownership and updates |
| Record | A stored instance of something the system tracks, such as a contact or an opportunity |
| Field or property | A named piece of information on a record, such as source, preferred date or owner |
| Association | A relationship between records, such as an opportunity linked to a contact |
| Stage | A position in a process, such as a sales opportunity awaiting a decision |
| Status | The current condition of an item, such as a task that is open, blocked or complete |
| Owner | The person or queue responsible for the next action; access permission is a separate question |
| API | An interface through which software can request data or actions from another system, within that system's rules |
| Webhook | An event notification delivered to a configured endpoint; the receiving system still needs to validate and handle it |
| Retry | Another attempt after incomplete work; the design should prevent a repeat from creating an unintended duplicate action |
| Human handover | A defined transfer of responsibility from automation to staff, including context and rules for automated activity |
How to use the explanations and examples
Definitions describe the concepts; practical examples show how to reason about them. An illustrative workflow is not evidence that a particular account supports every step. Check the actual product, plan, permissions and channel rules before implementation.
The reference guides on aiautomationphilippines.com are published by the same operator as this services site. They provide broader educational reading; links between the two are not independent endorsements.
If you are working through your own process, write down the starting event, information source, decision, action, expected result and exception. That small process map gives you a useful basis for learning, testing or comparing tools.