Workflow automation

Macros: A small click with a big effect

A macro is a small programme that can be called up at the touch of a button and automates processes in an application programme. A macro contains the combination of several instructions or chains of instructions. When the macro is called up, all the instructions it contains are executed in the defined sequence. High user-friendliness and fast implementation without programming skills are characteristics of macros.

Run routine tasks without errors

Why should you use macros? Clearly, to save time, as they automate recurring tasks. The error-free execution of a whole series of work steps should not be underestimated. How often does it happen to an employee in daily practice that he or she skips a work step, makes a mistake or clicks the wrong one when selecting text modules?

Example: With just one click, you can move a service request to the correct topic box, categorise the reason for the request, create and send a query to the accounting department and an interim reply to the customer, and also store a processing note.

Optimise sales processes

There is also potential in the automation of pre-sales activities in the order-to-cash process. Starting with the automatic pre-processing of quotation requests, to the filing and transfer of supplementary documents, clarifying correspondence, be it queries with the customer or the supplier, or automated follow-up queries on the quotation created.

Example: Read out relevant contents of a request for quotation from the email or an attached document at the push of a button and transfer them digitally to SAP or Dynamics.

Triggers open up new perspectives

Macros are particularly efficient when they are started automatically on the basis of events. Trigger events can be divided into time-based, internal and external triggers. Time-based triggers pay attention to processing and waiting times, but also to deadlines in emails and attachments. Internal triggers are based on defined actions within the INEXSO ERM, external triggers on those in connected systems.

Example: If a request has not been responded to within one working day, an interim notification is automatically generated to the sender, informing about the delay, and the ticket status is adjusted.