Can I change my delivery address?
The address can be changed before the order leaves the warehouse. Contact customer service and we will help you check what applies to your order.
Published article · General rules, no customer dataAI platform for customer service
You have already
answered the
question.
Let that answer help the next customer too. Supportifier builds your knowledge base from material you already have, you review what applies, and the same knowledge is used across your whole customer service — from the help centre to the team's inbox.
Start in one channel. The same knowledge follows when you expand.
One shared foundation SUPPORTIFIER
DocumentsWebsite & FAQPast tickets
Your verified knowledge baseYour answer. In the right place.We build the foundation. You review the knowledge.
- Public help centreFind the answer yourself
- AI formHelp before the ticket is sent
- AI and live chatAsk, and reach a person when needed
- Inbox & AI supportLet an agent take over
- Customer portalFollow their own tickets
Customer data when it is needed. Business systems are a separate source of current customer information — fetched in the right customer context and never placed in public articles.
The same knowledge. Different channels and permissions.
Help before a ticket exists.Self-service on your website
Support when the team takes over.The same reviewed knowledge
No separate knowledge base per channel.We help you build the foundation
01 — One knowledge base. All of customer service.
From self-service
to personal help.
Customers can find the answer themselves, ask in the form, talk to the chat or follow their ticket in the customer portal. When the team is needed, it continues from the same knowledge.
INTERACTIVE EXAMPLE · No question is sent. No customer data is fetched.
Before contact
The answer is where the customer looks.
A public help centre with searchable articles and categories. Customers find published knowledge without starting a conversation.
Self-service on your own website.
The same question in all five views:Can I change my delivery address?On your websiteEXAMPLE DATA
Help centreOpen to everyone
What do you need help with?
Can I change my delivery address?Search example
OrdersDeliveryReturns
Contact customer service
We will help you on.
An AI form on your website. Try it with a ready-made example question.
Your question · Example
Hi! I accidentally entered my old address. Can I change it?
An ordinary contact option remains. This is not a booking form and sends no ticket.
Your customer serviceAI and live chat · Example conversation
Can I change my delivery address?
Answer from the knowledge base
The address can be changed before the order leaves the warehouse. To check your particular order we first need to identify you and fetch the order status.
InboxAwaiting an agent
Incoming email · Example
Delivery address change
Context for the team
The customer wants to change the delivery address. For a personal answer the team needs to identify the customer and check order status.
AI support · For review
The address can be changed before the order leaves the warehouse. Check the customer's order status before confirming that the change can be made.
Customer data: needs checkingNo address has been changed and no answer has been sent. Handover and available context depend on the flow you roll out.
My ticketsSigned-in customer
Your tickets
Open tickets- Delivery address change#4182 · Updated todayWith customer service
- Invoice for order 55120#4166 · Updated last weekResolved
The conversation in ticket #4182
You
Hi! I accidentally entered my old address. Can I change it?
Customer service
The address can be changed before the order leaves the warehouse. We are checking where your order is and will reply in this ticket.
The customer portal shows the customer's own tickets. Internal comments, AI drafts and other customers' tickets are not shown here.
The same knowledge sourceDelivery address changeRead the source
Delivery terms: The address can be changed before the order leaves the warehouse.
One reviewed rule is used in all five examples. The public help centre shows published content only. Internal instructions and personal customer data are not public.
Different ways in — not five steps the customer has to pass through.
02 — The work behind the answersYou do not have
Change the knowledge.
You do not have
to write a new
knowledge base.
We gather and structure your documents, website and past customer tickets. You review what applies. That shared foundation is then used in the help centre, the AI form, the chat, the inbox and the customer portal — within each channel's permissions.
One change · Five usesSIMULATION
Change the knowledge.
Not four different systems.
See the difference between a proposal and published knowledge.
Delivery address changeVersion 1 · Published in the example
The address can be changed before the order leaves the warehouse.
All five views use the same published version. No real knowledge is changed.
Help centrev1
The address can be changed before the order leaves the warehouse. Contact customer service and we will help you check what applies to your order.
AI formv1
The address can be changed before the order leaves the warehouse. If you need help with your specific order, you can pass the question on to customer service.
Chatv1
The address can be changed before the order leaves the warehouse. To check your particular order we first need to identify you and fetch the order status.
Inboxv1
The address can be changed before the order leaves the warehouse. Check the customer's order status before confirming that the change can be made.
Portalv1
The address can be changed before the order leaves the warehouse. We can see where your order is and will write here in the ticket what applies to it.
Illustrative product view. Review, publishing, synchronisation and permissions are decided during rollout. No automatic or instant publishing is promised.
The questions show what is missing.
We help you fill the gaps. A single answer does not automatically become a new rule for every customer.
- An unanswered question reveals a knowledge gap.
- A suggested improvement is drafted from the source material.
- You review what should apply and be published.
- The updated knowledge can be used in the relevant channels.
03 — The support team's workspace
When the team takes over,
the workspace is
already here.
The ticket, the customer and the source material are in one place. The agent does not have to search four systems to be able to answer.
Tickets today · ExampleEXAMPLE DATA
| Ticket | Owner | Status | SLA |
|---|---|---|---|
| Delivery address changeDeliveryAI draft | Elin | In progress | 2 h left |
| Invoice missing for order 55120Invoice | Jonas | Waiting on customer | Paused |
| Return of a faulty itemReturn | Unassigned | New | 30 min left |
Selected row
Everything needed to answer.
- Owner and status
- Who owns the ticket and where it stands right now.
- Labels
- Topic and flow, so similar tickets can be followed as a group.
- AI support
- A draft built on the reviewed knowledge — for the agent to approve or rewrite.
- SLA
- How much time remains against the response time you have decided on.
Opening hours and staffing
Input for staffing. Not a schedule.
Based on inflow per hour and handling time, the system can show where the need is greatest. It is a suggestion to take a position on — Supportifier does not schedule staff and does not book working hours.
- 08–10High inflowSuggestion: 3 agents
- 10–14Even inflowSuggestion: 2 agents
- 14–17Lower inflowSuggestion: 1 agent
Illustrative product view with example data. Tickets, names, times and suggestions are invented.
04 — Follow-up
See what works.
Improve what
does not.
Follow-up should be usable for decisions: where the knowledge is enough, where it is not, and where the team's time goes.
- 1,240Tickets inAll channels
- 1 h 40 minMedian response timeFirst reply
- 38Waiting ticketsRight now
- 94%Within SLAOf answered
- 4.4 / 5Customer satisfaction312 responses
The AI's contribution
Two different things, counted separately.
612 ticketsAI-assisted answers
An agent received a draft, reviewed it and sent the answer. A person stood behind every answer.
184 ticketsAutomatically resolved tickets
The customer was helped without an agent stepping in — within the flows you have approved for automatic handling.
What the figures point to
The questions without answers are the most useful list.
- Can I change size after purchase?48 ticketsKnowledge gap — a proposal is ready for review
- When is the money taken?31 ticketsConflicting answers in two sources
- Do you deliver to Åland?12 ticketsMissing entirely from the material
Every figure on this page is example data to show the view. They are not measured results and not a promise of what you will achieve.
05 — On your website
On your website.
With your brand.
Customers should recognise where they are. The help can live in your own site, on your own address and in your own systems.
Widget, domain and API are part of the agreed arrangement. Scope and setup are covered before the start.
06 — Information from your systems
The policy is the same.
The customer's situation
is not.
The knowledge base describes the rules. A connection to your systems can add current order status, contracts or invoice information in the right customer context. Personal customer data does not belong in a public help centre.
Go through your connectionsCRMCustomer view
and contracts
and contracts
ERPOrder status
and invoices
and invoices
Existing helpdeskChannels
and ticket history
and ticket history
Examples of information sources. Support, permissions and scope are verified for each connection before rollout.
07 — A manageable first step
Start where the questions
already arrive.
You do not have to roll out everything at once. Start with self-service, the chat or the team's inbox. The next channel uses the same knowledge foundation.
Find your first step01
Supportifier
We set up the foundation.
We go through your sources, build the knowledge and prepare the chosen flow. You review the content that will be used.
02
Your team
You decide what is used.
Review articles and test answers before they reach customers. Choose what may be public and which questions should go to a person.
03
Together
We expand what works.
Add more channels without starting over on the knowledge. Customer data, permissions and limited automation are decided together.
The customer's experience
Dold Adress.
Dold Adress needed to handle a growing inflow of customer email without compromising on quality.
About the collaboration”Resultatet är kortare svarstider och ett team som får fokusera på det som verkligen kräver en människa.”
Translated from Swedish: ”The result is shorter response times and a team that gets to focus on what genuinely requires a human.”
08 — A clear arrangement
Know what is included.
Before you start.
The platform, the rollout and any integrations should be clearly described. We go through what you need and what can wait.
Go through your arrangementPlatform and operationAgreed scope
and volume
and volume
RolloutSources, knowledge work
and launch
and launch
IntegrationsSpecified connections
and ongoing responsibility
and ongoing responsibility
Pricing is based on your scope. We go through volumes, rollout and responsibilities before you take a position on an arrangement.
Next step
Which question have you
answered the most
times this week?
Bring it to a walkthrough. We show how the same answer can help the customer on your website and the team in the inbox.
Start from your own material.
Supportifier Knowledge Analysis shows where questions recur, which answers already exist and where you need to fill the gaps.
Your most common recurring questionsThe knowledge that can already be usedA concrete proposal for the next step
Before we meet
Fair questions.
Straight answers.
Do we need a finished knowledge base?
No. We start from the material you already have: past tickets, documents, your website and existing answers. We structure the knowledge and you review what should be used.
Do the help centre, the form and the chat need their own knowledge bases?
No. They use the same reviewed knowledge foundation as the team's inbox. You decide which content may be published or used in each channel. Updates follow your review and publishing process.
Will internal instructions and customer data become public?
No. Shared knowledge does not mean shared access. The help centre shows published content. Internal instructions and personal customer data should only be used where the right permissions and customer identification exist.
Can customers still reach a human?
Yes. The help centre, the form and the chat are different routes to help, not mandatory obstacles in front of the team. Which questions are handed over, and what context follows along, is decided during rollout.
Do we have to replace our current support system?
That is not our starting assumption. First we go through your channels and possible connections. Then we decide what can stay and what needs to change.
Does the AI have to send answers automatically?
No. You can start with draft answers that your team reviews. Automatic handling should only be used within the scope and controls you have decided on.
What happens when the source material is not enough?
Then the question should go to a person. It can also reveal a knowledge gap to fill. A new proposal is reviewed before it becomes applicable knowledge.