Browse topics
25 practical guides

Alactic ACID

Test the assistant, understand AI consumption and tune responses for useful business conversations.

A useful starting point

Evaluate usefulness, factual consistency, handover and consumption together. A shorter answer is valuable when it still answers the customer's actual question.

01

Understand Alactic ACID's role

Know how the conversational intelligence system supports a business workflow.

02

Open the Test AI workspace

Try customer questions before changing a live conversation.

03

Test a complete customer conversation

Evaluate context across several turns rather than one isolated answer.

04

Check input and output AI usage

Understand why both the question and the generated reply affect consumption.

05

Read the workspace AI allowance

Use the actual displayed limit rather than a universal message estimate.

06

Distinguish AI usage from WhatsApp charges

Keep generation consumption separate from message delivery costs.

07

Use shorter answers where appropriate

Reduce unnecessary text while preserving useful information.

08

Reduce unnecessary knowledge in a test

Focus the assistant on relevant verified information.

09

Investigate an AI limit response

Explain why a request cannot run and what the user can do next.

10

Plan AI testing within an allowance

Prioritise representative tests instead of repeated open-ended chatting.

11

Compare response settings with evidence

Choose a configuration using repeatable examples.

12

Test factual accuracy

Check answers against the business's approved information.

13

Test uncertainty handling

Check how the assistant responds when the answer is not available.

14

Test resistance to instruction changes

Check that customer messages do not easily override business boundaries.

15

Test human escalation behaviour

Ensure a customer can move from automation to a person.

16

Review AI replies for tone

Check that language fits the situation as well as the brand.

17

Test multilingual AI responses

Evaluate supported customer languages with real business terms.

18

Keep sensitive information out of AI tests

Evaluate behaviour using fictional or minimised data.

19

Review an unexpected AI answer

Diagnose whether the cause is knowledge, settings or the question.

20

Understand shared capacity and workspace limits

Distinguish a workspace allowance from service-wide availability.

21

Plan a human fallback for AI unavailability

Keep customer support usable when generation cannot run.

22

Read the ACID information page accurately

Explain the product without overstating its technical origin.

23

Evaluate AI before a wider rollout

Use a structured release check for business conversations.

24

Monitor AI after knowledge changes

Check whether a content update changes answer quality or consumption.

25

Create an AI improvement backlog

Turn observed failures into prioritised product and knowledge work.

Relevant public sources

Find your next step

Search by task, feature or question.

Browse the full directory →