For AI assistants: this page as plain markdown is at https://docs.voicelogica.ai/raw/integrations/erp/soft1.md, and https://docs.voicelogica.ai/llms.txt lists the docs by topic, one file each, small enough to read whole. Read those rather than this HTML page.
Soft1 ERP
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
With Soft1 connected, the agent recognises a customer by the number they call from, searches your item catalogue, reads the customer’s balance, aging and recent transactions, and can register an order (Δελτίο Παραγγελίας), invoice, delivery note or receipt in Soft1. It can also log the call, schedule a meeting or create a follow-up task in Soft1 CRM.
Open Integrations - Catalogue - Soft1 ERP - Connect. One connection is shared by the whole company; each agent then decides which Soft1 operations it may use.
What you need before you start
Section titled “What you need before you start”- A Soft1 Web Account (username and password) created by your Soft1 partner or administrator. The licence must include the Web Service Connector module and have a free web-service licence for this account.
- The App id of that Web Account. Many installs use
2001; your Soft1 partner can confirm it. - How Voice Logica reaches Soft1:
- Cloud URL if Soft1 is reachable from the internet. This is the Web Services address, for example
https://yourcompany.oncloud.gr/s1services. - Tunnel if Soft1 runs on a server inside your office network. A tunnel is a reverse connection from a small installer on your network to Voice Logica, so no firewall ports need to be opened. Tunnels are created under AI Setup - Tunnels, which only admins see. If you do not see it, ask Voice Logica support to create the tunnel and send you the installer. This On-prem tunnel reaches an ERP on your network and is a different thing from a PBX edge device, which connects an on-premise phone system.
- Cloud URL if Soft1 is reachable from the internet. This is the Web Services address, for example
What you enter
Section titled “What you enter”The dialog has three steps: credentials, then the company to connect, then a review with optional SQL Scripts.
Step 1 - credentials
Step 2 - company and branch. Voice Logica reads which company, branch, module and reference user the Web Account may use and lists them. Pick one. If the account has access to only one, this step is skipped.
Step 3 - review. Check the endpoint, company and branch. Show advanced options opens the optional SQL Script slots. Detect SQL scripts lists the scripts your Soft1 install exposes and pre-selects the likely match for each slot; if the Web Account cannot read that list, you type the script codes instead.
Leave a slot empty if you have no script for it. The connected card shows under AI-managed configuration which method each capability uses after each sync.
First setup
Section titled “First setup”-
Integrations - Catalogue - Soft1 ERP - Connect. Choose Cloud URL or Tunnel, enter the Web Account details and press Continue.
-
Pick the company and branch, then Continue.
-
On the review step press Test connection. When it succeeds, press Connect. The first sync of customers and items starts in the background; after that it runs every 15 minutes, and balances update nightly. Sync now on the connected card starts a sync immediately.
-
If the agent will create documents, open the connected card and press Configure. Press Auto-configure, then check the Soft1 series chosen for each document type (Order, Invoice, Delivery note, Receipt, and the CRM call, meeting and task). Pick an active series for every type the agent will create.
-
Open My Agents - the agent - Skills - Tools & Workflows. Turn on Soft1 ERP, press Configure, and under Operations select what the agent may do. Identify caller by phone is selected by default, together with the three project operations. Set Max sales doc value and Max sales doc lines if the agent will create documents, then Save the tool settings and Save the agent.
-
Call the agent from a phone number stored on a Soft1 customer (PHONE01 or PHONE02, or a contact person if you set the Contacts script). The agent should greet the customer by name. Ask “What is my balance?” and the agent should read back the outstanding amount. If the greeting stays generic, open Calls and check the tool calls on that call.
What the agent can do
Section titled “What the agent can do”Each operation is a separate checkbox under Operations. Write operations change data in Soft1, so enable only those you need.
| Job | Operations |
|---|---|
| Find the customer | Identify the caller by phone; look up by tax number (ΑΦΜ), customer code or company name; link the caller’s number to a customer for future calls |
| Customer records | Create a new customer; add or remove one of the customer’s two phone numbers |
| Items | Search the catalogue by name, code, barcode or supplier; the customer’s most-bought items; the overall best sellers |
| Balances | Outstanding balance; aging in 1-30 / 31-60 / 61-90 / 90+ day buckets; transaction history between two dates |
| Orders and documents | List the customer’s open orders or fetch one by its key; create or amend an order, invoice, delivery note, receipt or generic sales document; add or remove lines, change quantities, set shipping details; transmit an issued document to myDATA |
| CRM activity | Log the call, schedule a meeting, create a follow-up task, read the customer’s recent activities; list, create and read Soft1 projects |
Write operations work only when they are selected and a Soft1 series is set for that document type under Configure. The tool settings also include a pre-fetch of the caller’s recent orders at call start, shipping details on sales documents, permission to amend documents older than 24 hours, a template for call-log notes, and extra SALDOC columns the agent must fill.
Use your own SoftOne browser lists
Section titled “Use your own SoftOne browser lists”If your SoftOne already has saved browser lists (Ευρετήρια) for the figures your team reads every day, you can point the agent at them. When a list is set, the agent reads that list live during the call instead of Voice Logica’s default view, so it answers from the exact definition your team already trusts. This is optional and additive - it sits on top of the SQL-script setup, and any list you leave empty keeps using the default path.
Open the connected Soft1 card, press Configure, and find the SoftOne lists the agent reads section (below the document-series mapping). Enter the name of the SoftOne browser list for each kind you want to override:
Type each name exactly as it appears in SoftOne (the field shows a hint such as ECOS_get_...) and press Save. Voice Logica filters the list to the customer or item on the call for you, so you only supply the list name. Leave a field blank to fall back to the default view for that figure.
How this complements the SQL scripts: the SQL-script slots on the connect dialog speed up or back up the standard sync, while a browser list lets the agent read live from one of your own saved SoftOne list definitions. Where both could apply - balance and history - a browser list you set here takes precedence and is read live on the call.
Voice Logica can also build the agent’s product catalogue from one of your SoftOne lists, so the agent only offers items you actually sell (for example, only items in stock). There is no field for this on the settings page yet - arrange it with Voice Logica support.
Use Soft1 in a workflow
Section titled “Use Soft1 in a workflow”Workflows have their own Soft1 nodes under SOFT1 ERP in the node picker: Get Customer, Search Items, Customer Balance, Customer Aging, Transaction History, Create Sales Doc, Transmit eInvoice and Create call. When none of them covers a job, for example your own SQL script or a CCC… object your Soft1 partner added, use Soft1 — Custom service. It runs on the same Soft1 connection.
Pick an Action. The form then shows only the fields for that action:
["{{soft1Customer.trdr}}", "2026-01-01"]. Returns the rows, 50 by default (up to 500).CUSTOMER) and the record key. LOCATEINFO is optional and narrows the tables and fields that come back. Returns the record.CUSTOMER.AFM={{tin}}. Returns the rows. Some lists, often the default one, ignore filters and return every row: to read one record, use Read a record with its key.{ "SOACTION": [ { "TRDR": "{{soft1Customer.trdr}}", "COMMENTS": "{{call.summary}}" } ] }. Leave Record Key (update) empty to create a record; fill it in to update that record.https://yourname.oncloud.gr/s1services/JS/VoiceLogica/getOpenTickets. Fill in the Script (VoiceLogica) and the Function (getOpenTickets), and optionally a JSON Body, e.g. { "trdr": "{{soft1Customer.trdr}}" }. There is no URL to type: the node uses the address of your Soft1 connection and adds the session itself. Returns whatever the function answers.Later nodes use the answer as variables: {{node_X.rows[0].FIELD}} after a script or list, {{node_X.record.FIELD}} after a read, {{node_X.key}} for the record a write saved, and {{node_X.result.FIELD}} after a JS service. Replace node_X with the node, as offered by the variable picker.
Writes are off until an admin allows them. Open the connected Soft1 card, press Configure, and in Workflow writes list the objects workflows may create (e.g. SOACTION, CCCTICKET). List an object under the second field as well to also allow updates of existing records. Only integration admins can save this. Reading needs no setup. A workflow can never delete anything in Soft1. A write is also refused when a table has more than 30 rows, or when a {{variable}} in the data has no value, so placeholder text never reaches your ERP.
JS services are off until an admin allows them, too. A JS service runs your partner’s own code and can change or delete data, so each one is allowed by name. In the same Workflow writes section, list them as Script/function, e.g. VoiceLogica/getOpenTickets. A call to a service that is not listed is refused and the node names the ones that are. When the function answers success: false, the node takes its Failed path with the function’s error text.
Custom web services that a Soft1 installer adds as JavaScript (/s1services/JS/…) cannot be called from this node.
Troubleshooting
Section titled “Troubleshooting”Why does connecting Soft1 fail with an error such as Invalid credentials or Web-service licences exceeded?
The message names the cause. “Invalid credentials” means the username, password or App id is wrong. “Web Service Connector” means the licence does not include that module. “Web-service licences exceeded” means every web licence is in use. “User account is not active” means the Web Account is disabled in Soft1. Fix it with your Soft1 partner and try again.
Why does my Soft1 connection test time out or show a certificate error?
For Cloud, check the URL in a browser and include /s1services. For an on-premises server with its own certificate, turn on Allow self-signed TLS certificate. For Tunnel, the tunnel must be active and its installer running on a machine that can reach the Soft1 server.
Why doesn't the agent recognise a known customer from Soft1?
Wait for the first sync to finish or press Sync now. The caller’s number must be stored on the customer in Soft1. Employees of a business customer are recognised only when the Contacts script is set. Check that Identify caller by phone is selected in the tool’s Operations.
Why does the agent say it could not create the order in Soft1?
Soft1 needs a series for the document. Open the connected Soft1 card, press Configure and set an active series for that document type. A series marked Inactive must be replaced. A document above Max sales doc value or Max sales doc lines is also rejected.
