How to set up ai agents for erp software solutions

You need three things:

• A Chatref account – new accounts get $50 in free credit with no credit card required, and credit never expires. Sign up at https://app.chatref.ai.
• Your ERP support content – upload PDFs, point to your help-centre URLs, or feed in a sitemap of your documentation site. The agent answers only from what you give it, so the better the content, the sharper the responses.
• Website or app access – you will drop a small embed snippet into the pages where your ERP users need support, such as the login screen, settings panels, or your support portal.

If you are supporting multiple ERP modules (finance, HR, supply chain, CRM), you might create separate agents for each, but a single agent trained on your full help centre often works well for consolidating repetitive requests. Later, conversation insight digests will tell you which topics surface most often so you can refine your docs.

1. Add your ERP content Log in to Chatref, go to an agent or create a new one, and open the Knowledge tab. Upload your PDF manuals, paste URLs to your ERP onboarding guides, and optionally submit a sitemap of your support site. Chatref learns only from this material – no internet search, no guesswork.

2. Create and brand the agent Under the Agent tab, give the agent a name (for example “Acme ERP Assistant”). Set the primary language and pick your brand colour. Write a short welcome message like “Ask me anything about setting up or using Acme ERP.” The look and voice come from these settings, so take a moment to match your brand.

3. Customise the behaviour (optional) You can add a custom system prompt to steer tone – for instance, “Answer in a concise, professional style, and always provide step numbers from the official guide.” This is where you inject your ERP-specific service voice. If a question cannot be answered from your docs, you can also define a fallback reply.

4. Embed the widget From the Embed tab, copy the snippet – it’s a single <script> tag. Paste it into the HTML of any page where you want the widget to appear, right before the closing </body> tag. Make sure you allowlist the exact domain in the Chatref dashboard so the widget can load (origin‑allowlisting prevents unauthorised usage).

   <script
     src="https://app.chatref.ai/widget.js"
     data-agent-id="YOUR_AGENT_ID"
     defer
   ></script>
   

5. Configure handoff (optional but recommended) In the Settings area, enable the shared inbox so a human team member can take over a conversation when the agent cannot resolve the request. The entire chat history transfers, so no one has to repeat information. For ERP support, this is valuable when a question involves account-specific data the agent cannot see.

Use Chatref’s live playground to test without deploying to your site. Ask real questions your customers ask:

• “How do I import my chart of accounts?”
• “What permissions do I need to run the month-end close?”
• “Why is my GL balance not matching?”

Check that each answer references a specific section from your uploaded content. If an answer is off, revisit the knowledge base and add more granular documents; sometimes a single long PDF is less effective than smaller, topic‑focused pages.

Then open your website where the widget is embedded and try the same questions. Confirm the widget appears, the first message matches your welcome text, and user data (if lead capture is on) logs correctly.

The agent gives generic or irrelevant answers This almost always means the knowledge base is too thin or the right document wasn't added. Upload your setup walkthroughs, error‑resolution guides, and permission tables. Make sure the URLs you added are publicly reachable and not behind a login.

The widget does not load Verify the domain you added the snippet to matches an entry in the Allowed Origins list inside the agent’s settings. Also check if your web application enforces a strict Content Security Policy that blocks external scripts – whitelist app.chatref.ai if needed.

Answers show links that don't work If your docs contain relative links or internal-only URLs, the agent can repeat them, but those links might not resolve from the customer’s context. Use absolute URLs in your source content or remove broken references from uploaded files.

The agent’s tone doesn't feel right Adjust the custom system prompt in the agent settings. Try a short instruction like “Use a helpful, patient tone and refer to customers as ‘you’.” The agent will then ground all replies in your docs but frame them under that tone.

Human handoff never triggers Open the conversation inbox to confirm the shared inbox feature is enabled and a team member is active. The handoff route depends on you defining an escalation rule or a keyword trigger; without it, the agent will keep trying to answer.

For a deeper look at how this fits into the broader support workflow for ERP platforms, read about ERP Software Support.

What causes ERP software support problems?

The most common root cause is an under‑resourced team handling high volumes of repeated, predictable questions about setup, data imports, permissions, and module-specific workflows. When the only support path is a human emailing back or pointing to a searchable knowledge base, reply times spike after onboarding waves, inconsistencies creep in, and the team burns out. Additionally, documentation that is incomplete or hard to navigate amplifies the problem.

How do I improve ERP software support?

Introduce an AI agent trained on your ERP's own documentation. The agent handles routine questions instantly and consistently, reducing ticket volume and letting your support staff focus on complex cases. Use the conversation insights that come from the agent – top question categories, failed answers – to identify where your guides need updating, then refine your content. This creates a loop where every interaction improves the next one.