Follow

2026.11.01 - What's New at Juice

This is the October edition in an ongoing series summarizing everything released or updated each month across your CEO Juice suite. Processes marked ⭐New are tested and ready to activate. Updated processes include a summary of what has changed in the latest version. Click any integration title to view its full documentation.

Online Payments Portal

Your AR team now gets a nightly round-up from the payments portal of anything that needs following up, from failed payments to invoices autopay skipped.

Juice Payments gives your customers an online portal to pay their invoices and set up autopay, with payments syncing back into e-automate. NMI is the payment gateway, and you can choose your own payment processor.

What changed: A new nightly email summarizes the last 24 hours of activity on your Juice Payments portal: payment failures and rejections, late returns, payments that didn't sync with e-automate, new clients and new autopay setups, and invoices that autopay skipped, with the reason. Each item shows the customer, the invoice and the details you need to follow up. It's on by default and goes to the recipients on your ID669 subscription. Choose which events you receive, or turn the email off, with Variable W, or just ask us and we'll update it for you.

DCA Updates

A landmark month for DCA development. EKM becomes our first live "Phase Two" integration, keeping your DCA and e-automate in step automatically in both directions. HP SDS / MPS Monitor (ID311) is in beta for Phase Two and KPAX (ID76) is coming soon. See the DCA API Integrations Overview for what each DCA supports - we recently fully updated our diagram which says what's live, what's in progress, and what's in beta.

This process integrates with the EKM API and is required for any other CEO Juice processes that will leverage EKM data.

What changed: Phase Two is here, so you no longer need to update the same details by hand in both systems. IP and MAC addresses come into e-automate from EKM, while equipment numbers, customer and equipment messages, and managed status (based on the e-automate contract status) go back to EKM. You choose which of these it manages with Variable X. It starts in test mode, emailing your ID448 recipients what it would change, so you can check the results before it goes live. Additionally, sales order integration, which turns EKM low toner alerts into e-automate sales orders through ID634, is in beta testing and coming soon.

Reports

Survey Results gets a major update this month, with a new Executive Overview, comment sentiment analysis and an Insights panel on every page. Financial Insights can now show profitability by customer, and the Financial Benchmarking Model gets a new page for checking your GL account mapping.

There's already a survey dashboard built into our website once you log in, but if you want to really slice and dice your survey responses, the Power BI version is the way to go. It also lets you build an executive dashboard combining survey results with your other financial benchmarks.

What changed: New Executive Overview, CM Calls Without a Survey and Comment Sentiment pages, and Key Influencers has been rebuilt to group results into clusters by reporting period. Every page now has a slide-in Insights panel, and Smiley Faces results have been fixed.

Compares your financial performance against the industry benchmark models from Bering McKinley or Tom Johnson, pulling directly from your e-automate transactions. A Financial Cockpit shows where you're hitting or missing target, with company-versus-model comparisons, scoring by branch and department, and drill-through to the transactions behind every number. Requires your financials to be mapped through ID893.

What changed: A new Model / Account Mapping page shows how each GL account rolls up into the financial model, for both models, so you can spot unmapped or misassigned accounts before they distort your results. It's useful at setup, after adding new GL accounts, or whenever the numbers look off.

A financial reporting dashboard covering your full financial picture across 50+ report pages: income statement, balance sheet, cash flow, budget vs actuals, financial ratios and year-over-year comparisons, all pulling directly from e-automate transactions, with drill-through to the GL entries behind every number. Includes SG&A analysis and forecast vs budget tracking.

What changed: Every Income Statement page can now be filtered by customer type, such as Government or Major Account, or by individual customer, and a Customer Profit view breaks revenue and costs down by customer type, including anything not tied to a properly classified customer. General Ledger Details now shows the department, Budgeted Groups adds a second account group, trend charts show month labels, and dates use one consistent format throughout.

Other Integrations

New reference apps give your developers a head start on building a service call sync with the Juice API, and the ConnectWise contracts sync gets clearer error emails and new options. Plus a new Salesforce Order Sync that brings your equipment deals across, ready for ID634 to turn into e-automate sales orders.

If your sales team closes equipment deals in Salesforce, ID209 saves you keying them into e-automate a second time. Every 10 minutes it pulls your deals from Salesforce and holds them in a table shared with e-automate, but it doesn't create anything itself. ID634 Sales Order Import Utility, a required subscription, reviews those deals and creates the sales orders in e-automate. There is currently a waitlist for onboarding.

Access to the Juice API for e-automate. It's a secure doorway to your data that lets your larger customers or third parties build integrations with their own ticketing and ordering systems. Service calls and sales orders can then be entered in either system and stay in sync. Note this is the API itself, not a finished integration. The connection is built by you, your customer, or a third party.

What changed: New reference apps to help you get started. They show how to sync service calls between e-automate and ServiceNow through the Juice API, with versions in .NET, Node.js, PowerShell and Python, plus one that runs inside ServiceNow itself. They're a starting point for your developer rather than a finished integration, and you can download them from GitHub.

Takes agreement invoices from ConnectWise and uses them to create and update contracts in e-automate, with the ConnectWise agreement acting as the master for contract billing. The base amount and additions push across each time the agreement is invoiced, and the sync will create the contract and any missing items for you using templates. There are options to push data back the other way too, including the e-automate contract number and invoice number, and marking the ConnectWise invoice as paid once it's paid in e-automate. Requires ID747.

What changed: Error emails are now clearer, naming the agreement, invoice or billing cycle involved. This covers billing cycles not found in e-automate, linked contracts that have been deleted, and ConnectWise custom field issues. A new warning also flags when a contract number already held in a ConnectWise custom field is overwritten. A new option, available on request, lets you use the ConnectWise product description for item descriptions instead of the customer invoice description. Also includes performance improvements.

Alerts and Data Housekeeping

An update to ID53, which can now keep more of your team in the loop on service calls for the customers and equipment that matter most.

Got a key account your service manager wants to keep a close eye on? When a corrective or preventive maintenance call is opened for a customer or piece of equipment you've flagged, ID53 emails the nominated contact, whether that's a service manager, sales manager or owner, and keeps them updated as the call is dispatched, arrives and is completed.

What changed: Runs faster, and if Pending is one of your trigger statuses, new calls now always send the alert, even if they've already been dispatched by the time ID53 runs. Five new options let you also send the alert to the customer's sales rep and their manager, the technician on the call and their manager, or whoever created the call. A new Variable X lets you limit the alert by the call's branch.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk