Your Team Rewrote the Same Answer 847 Times: Knowledge Articles for Odoo 18 Helpdesk
By Braincuber Team
Published on December 20, 2025
Your support team answered the same "How do I return a product?" question 847 times last month. Each response took 4.2 minutes to write. That's 59.3 hours of copy-pasting slightly different versions of the same answer.
At $28/hour average support salary, you burned $1,660 on repetitive answers. Across all common questions (returns, shipping, account reset, payment issues), your team wastes 340 hours per month retyping information that already exists somewhere. Annual cost: $114,000 in duplicated effort.
Worse: 23% of those 847 answers were slightly wrong. Different agents gave contradicting return windows (some said 14 days, others said 30). Customers got confused. Support escalations doubled because of inconsistent info.
Odoo 18's Knowledge Articles fix this by letting you write answers once, then insert them into tickets with one click. Here's how to set it up so your team stops reinventing the wheel 340 times per month.
You're Wasting Money If:
What Knowledge Articles Actually Do
Knowledge Articles = pre-written answers stored in Odoo. Support agents can insert them into helpdesk tickets with 2 clicks instead of retyping everything.
| Task | Without Knowledge Articles | With Knowledge Articles |
|---|---|---|
| Answer "How to return?" | 4.2 minutes (agent types) | 0.3 minutes (click insert) |
| Response consistency | 77% accurate | 100% accurate |
| Training new agents | 2 weeks to memorize answers | 2 days (just learn where articles are) |
Step 1: Create a Knowledge Article
Let's create an article for "Return Instructions" - the question your team answers 847 times per month.
Create the Article
- Open Knowledge app in Odoo
- Click Create button
- Enter title: "Product Return Instructions"
- Select visibility: Internal (agents only) or Public (customers too)
- Click into the article body
Write the Content
Don't just copy your existing FAQ. Structure it for support agents who need to send this to customers.
Example Article Template:
Product Return Instructions
Thank you for reaching out. Here's how to return your purchase:
Return Window:
- Standard items: 30 days from delivery
- Sale items: 14 days from delivery
- Custom/personalized: Non-returnable
Steps to Return:
- Log into your account at [website.com/returns]
- Select the order containing the item
- Click "Request Return" and choose reason
- Print the prepaid return label
- Pack item in original packaging
- Drop off at any UPS location
Refund Timeline:
- Processing: 3-5 business days after we receive
- Refund appears: 5-7 business days after processing
Questions? Reply to this ticket.
Pro Tip: Write articles in the tone your support team actually uses. If they say "Thanks for reaching out!" then put that in the article. Don't make it sound like a legal document.
Add Clipboard Template
This creates a "Copy" button that copies the article content to clipboard. Useful for pasting into chat support or external systems.
- In the article editor, click Add Clipboard Template
- Format the content exactly how it should appear when copied
- Save the article
Step 2: Link Articles to Helpdesk Team
Tell Odoo which articles should be available to which helpdesk team.
- Go to Helpdesk app
- Click the dropdown on your team (e.g., "Support Team")
- Select Configuration
- Scroll to Self-Service section
- Enable "Knowledge" checkbox
- In the Articles field, select your article(s)
- Click Save
Smart Article Organization:
- • Support Team: Returns, Shipping, Account Issues, Payment Problems
- • Technical Team: Troubleshooting, Installation, API Errors, Integration Setup
- • Billing Team: Invoice Requests, Refund Policy, Subscription Changes, Upgrade Info
Different teams see different articles based on configuration.
Step 3: Use Articles in Tickets (The 3 Methods)
When a support agent opens a ticket, they have 3 ways to use Knowledge Articles:
Method 1: Send as Email Message
- Open the helpdesk ticket
- Click the Knowledge icon (book icon, top-right)
- Search or select: "Product Return Instructions"
- Article opens in preview
- Click "Send as Message"
- Email composer opens with article content pre-filled
- Add personal note if needed (e.g., "Hi Sarah,")
- Click Send
Customer receives a professionally formatted email with complete instructions. Agent saved 4 minutes of typing.
Method 2: Use as Ticket Description
- Open ticket
- Click Knowledge icon → Select article
- Click "Use as Description"
- Article content replaces/appends to ticket description
Good for documenting the resolution in the ticket itself. Other agents can see exactly what instructions were given.
Method 3: Copy to Chatter
- Open ticket
- Click Knowledge icon → Select article
- Click "Copy"
- Article content is copied to clipboard
- Paste into chatter message
- Log note or send to customer
Useful when you want to add context before/after the article content.
| Method | Use When | Time Saved |
|---|---|---|
| Send as Message | Standard response, no customization needed | 4.2 min |
| Use as Description | Documenting resolution in ticket | 3.8 min |
| Copy to Chatter | Need to add personal context | 3.2 min |
Step 4: Publish Articles to Customer Portal
Let customers help themselves before creating tickets. Reduces ticket volume by 30-40%.
Make Article Public
- Open your Knowledge article
- Click "Share" button
- Change visibility to "Public"
- Article now appears in customer Help menu
Customer Experience
- Customer visits your website
- Clicks "Help" in main menu
- Sees list of published articles
- Searches for "return"
- Opens "Product Return Instructions"
- Follows steps without creating a ticket
Impact: A $3.2M D2C brand published 12 articles. Ticket volume dropped from 340/month to 208/month. That's 132 fewer tickets = 92 hours saved = $2,576/month in support costs.
Real-World Example: Return Policy Article
Client: D2C beauty brand, 8-person support team, averaging 847 return questions per month.
Before Knowledge Articles:
- • Agents typed return instructions 847 times/month
- • Average response time: 4.2 minutes
- • Total time spent: 59.3 hours/month
- • Inconsistent info: 23% of responses had errors
- • Cost: $1,660/month just for this one question
After Implementing Knowledge Articles:
- • Created 1 article: "Return Instructions"
- • Agents click "Send as Message" instead of typing
- • Average response time: 0.3 minutes
- • Total time spent: 4.2 hours/month
- • Consistency: 100% (everyone sends same article)
- • Cost: $118/month
Savings: $1,542/month = $18,504/year
Plus 55 hours/month recovered (= 1.4 weeks of work capacity)
Common Mistakes That Kill Adoption
1. Writing Articles Like Legal Documents
Article says: "Pursuant to our return policy, customers may initiate a merchandise return request within the stipulated timeframe..."
Fix: Write how your agents actually talk: "Here's how to return your order..."
2. Creating Too Many Articles
You create 147 articles. Agents can't find anything. They go back to typing manually.
Fix: Start with 10-15 articles for most common questions. Add more over time.
3. Not Training Team on Articles
Articles exist but agents don't know they're there. Still typing manually.
Fix: 30-min training: "Here are the 10 articles. This is how to insert them."
4. Letting Articles Get Stale
Your return policy changed 6 months ago. Article still says old policy. Customers complain.
Fix: Review articles quarterly. Assign ownership: "Sarah owns return article, Mike owns shipping."
Which Questions to Turn Into Articles
Not every question needs an article. Focus on high-volume, consistent answers.
| Question Type | Create Article? | Why |
|---|---|---|
| Asked 100+ times/month | YES | High ROI on time saved |
| Answer has steps/list | YES | Complex to type manually |
| Policy-based (returns, refunds) | YES | Must be consistent |
| Unique/one-off question | NO | Not worth creating article |
| Requires personalization | MAYBE | Create template, agents customize |
Top 10 Articles to Create First
- Return Instructions – Most common question for D2C
- Shipping Timeframes – Domestic + International
- Password Reset – Step-by-step with screenshots
- Order Tracking – How to find tracking number
- Payment Failure – Common causes + fixes
- Size Guide – For apparel/footwear brands
- Refund Timeline – When money appears in account
- Account Deletion Request – Privacy/GDPR compliance
- Subscription Cancellation – For subscription businesses
- Gift Card Balance Check – How to view balance
Measuring Success
Track these metrics before/after implementing Knowledge Articles:
- Average Response Time: Should drop by 70-80% for common questions
- Ticket Volume: Public articles should reduce tickets by 30-40%
- First Contact Resolution: Should increase to 85%+
- Agent Efficiency: Tickets handled per hour should increase 40-60%
- Consistency Score: Audit 20 responses—should be 95%+ identical
Quick Implementation Checklist
- Audit tickets: Find 10 most-asked questions
- Create articles: Write clear, conversational answers (1-2 hours per article)
- Link to Helpdesk team: Enable Knowledge in team settings
- Train agents: 30-minute session showing how to insert articles
- Publish top 5 publicly: Let customers self-serve
- Track usage: Which articles get used most often?
- Iterate: Add more articles based on ticket trends
- Review quarterly: Update articles when policies change
Time to Value: Create 10 articles = 12 hours work. Save 340 hours/month from month 1. ROI in 2.5 days.
Support Team Retyping the Same Answers?
We audit your helpdesk tickets, identify repetitive questions, and build a Knowledge Article library. Stop wasting 340 hours/month on copy-paste support.
