{"id":542,"date":"2025-12-07T20:56:35","date_gmt":"2025-12-07T20:56:35","guid":{"rendered":"https:\/\/www.aboutflow.co.za\/?page_id=542"},"modified":"2025-12-08T10:41:48","modified_gmt":"2025-12-08T10:41:48","slug":"faq","status":"publish","type":"page","link":"https:\/\/www.aboutflow.co.za\/?page_id=542","title":{"rendered":"FAQ"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Frequently Asked Questions<\/h1>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

About AboutFlow<\/h4>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Understanding what the platform does and how it fits your organisationNew around here ? Start With the Basics<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t
\n
\n\n \n
\n
\n \n \n What is AboutFlow?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

AboutFlow is a business process management platform that lets organisations design, run, and improve process driven business applications. It replaces paper forms, email threads, and spreadsheet driven workflows with guided digital processes that connect to your existing systems.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Does AboutFlow replace our ERP or finance system?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

No. AboutFlow sits beside your ERP or finance system, not in place of it.<\/p>

Your ERP keeps doing what it does best, such as core finance, stock, or billing. AboutFlow handles the real life workflows around those transactions, such as approvals, checks, handoffs, and exceptions, then passes the right data into and out of the ERP.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n How is AboutFlow different from basic workflow tools or forms apps?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Basic tools often give you forms and simple approvals. AboutFlow is built for full process driven applications.<\/p>

This means you get:<\/p>

- A full life cycle from design to deployment<\/p>

- Strong integration to ERP and line of business systems<\/p>

- Version control and change management<\/p>

- Reporting and analytics on process performance<\/p>

- A security model that mirrors your organisation<\/p>

It is suited to teams that need more than a simple \u201csend form for approval\u201d pattern.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n What problems does AboutFlow help us solve?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Common problems include:<\/p>

- Approvals and requests stuck in personal inboxes<\/p>

- Repeated data capture into multiple systems<\/p>

- Poor visibility of who must do what and by when<\/p>

- Weak audit trails for decisions and documents<\/p>

- Long IT backlogs for process changes<\/p>

AboutFlow lets you turn these weak points into clear, repeatable processes.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n What's The Difference Between Annual & Monthly Billing <\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Lorem ipsum dolor sit amet, consectetur adipiscing elit, seddo eiusmod tempor incididunt ut
labore et dolore magna aliqua. Ut enim ad minim veniam.Lorem ipsum dolor sit amet,
onsectetur adipiscing elit, seddo eiusmod tempor incididunt ut labore et dolore
magnaaliqua. Ut enim ad minim veniam.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Who it is for<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Popular starting points include:<\/p>

- Human resources, for onboarding, leave, and case management<\/p>

- Supply chain, for supplier onboarding, requisitions, and invoice approval<\/p>

- Projects, for charters, risks, changes, and timesheets<\/p>

- Asset management, for registers, surveys, and disposals<\/p>

- Governance, risk, and compliance, for risks, controls, and policies<\/p>

Once one area works well on AboutFlow, clients often add more departments.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Is AboutFlow only for technical teams?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

No. IT plays an important role, especially for integration and governance, but business teams are involved in design and often maintain many processes using low code and no code tools.<\/p>

The goal is shared ownership, where process owners and IT work together.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n <\/div>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Implementation and projects<\/h4>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

How we scope, design, and deploy processes that work for you<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t
\n
\n\n \n
\n
\n \n \n How do we start an AboutFlow project?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Most projects start with one high impact process. The usual steps are:<\/p>

1. Process discovery workshop<\/p>

2. Solution design inside AboutFlow<\/p>

3. Integration and configuration<\/p>

4. Testing with real scenarios<\/p>

5. Training and go live<\/p>

During a demo or scoping call, we help you choose the best starting process.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n How long does it take to get value from AboutFlow?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Timelines depend on the process and the number of systems involved.<\/p>

Clients who begin with one well chosen process often see a first solution running in a short period, then extend the platform to more processes once they are comfortable.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Do you help us model and improve our current processes?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Yes. A key early step is understanding how you work today. Together we:<\/p>

- Map the current process in plain language<\/p>

- Highlight problems such as handoffs, delays, and unclear steps<\/p>

- Agree on a future process that AboutFlow will support<\/p>

This means the digital process reflects real work rather than a theory.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Can we start small and grow later?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Yes. Many organisations start with a single department or process, then grow into a wider platform across HR, supply chain, projects, assets, and GRC.<\/p>

The platform is built to add processes and users over time.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Do you offer pilot or proof of concept projects?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Yes. In many cases we run a pilot or proof of concept around one process. This lets you see AboutFlow in your own setting before a broader roll out.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n <\/div>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Technology and integration<\/h4>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Platform architecture, deployment options, and connecting to your existing systems<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t
\n
\n\n \n
\n
\n \n \n What technology does AboutFlow run on?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

AboutFlow runs on a Microsoft based stack. You can deploy it:<\/p>

- On your own servers, for example Windows Server and SQL Server<\/p>

- As a hosted shared solution<\/p>

- As a dedicated hosted solution<\/p>

Your IT team can choose the option that fits your policies and risk profile.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Which systems can AboutFlow integrate with?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

AboutFlow integrates with a wide range of systems, for example:<\/p>

- ERP and finance systems such as PhoenixERP, Acumatica Cloud ERP, Sage 200 Evolution, Sage Intacct, Xero<\/p>

- Municipal and sector specific systems<\/p>

- Microsoft 365 services, including SharePoint, Teams, Outlook, Power Automate, and Excel<\/p>

Integration is handled through the Integration Framework and other tools in the platform.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Does AboutFlow support APIs?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Yes. AboutFlow can use and expose APIs so that it can exchange data with other applications. This is handled in a controlled way to keep data consistent with your core systems.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Can we use AboutFlow with Microsoft 365?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Yes. Many clients use AboutFlow with Microsoft 365. Typical patterns include:<\/p>

- Storing documents in SharePoint<\/p>

- Sending notifications through Outlook<\/p>

- Using Teams for collaboration around processes<\/p>

- Triggering or responding to Power Automate flows<\/p>

This is helpful if your organisation already runs on Microsoft tools.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n <\/div>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Users, security and compliance<\/h4>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Access control, audit trails, data protection, and meeting regulatory requirementsNew around here ? Start With the Basics<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t
\n
\n\n \n
\n
\n \n \n How are users and roles managed in AboutFlow?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

AboutFlow includes a Security Framework that lets you:<\/p>

- Mirror your organisation structure and roles<\/p>

- Decide who can view, edit, approve, or administer each process<\/p>

- Restrict access to sensitive records and tasks<\/p>

This keeps control aligned with your internal authority rules.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Does AboutFlow keep an audit trail?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Yes. AboutFlow records:<\/p>

- Who started each process<\/p>

- Each task, approval, and change<\/p>

- Timestamps for actions<\/p>

- Linked documents and comments<\/p>

This gives you a clear history for audits, reviews, and investigations.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Where is our data stored?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Data location depends on your deployment choice:<\/p>

- On premises, on your own servers and within your own network<\/p>

- Hosted, in agreed data centres that match your policies<\/p>

During scoping we discuss data residency, backup, and recovery expectations and align them with your standards.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n How does AboutFlow handle backups and disaster recovery?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

The platform uses standard Microsoft database and server tools for backup and recovery. In a hosted setup, backup and recovery form part of the service design. On premises, your own IT team manages this using agreed guidance.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Is AboutFlow suitable for regulated industries?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Yes. AboutFlow is used in sectors such as finance, government, energy, healthcare, and utilities, where process control and audit trails matter.<\/p>

We work with your compliance and IT teams to align deployment and process design with your regulations.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n <\/div>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Low code, no code and ownership<\/h4>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Empowering business users while maintaining IT governance and version control<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t
\n
\n\n \n
\n
\n \n \n Do we need developers to build processes in AboutFlow?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

For complex processes and integrations, developer skills are helpful. At the same time, many parts of the platform are designed for low code and no code configuration.<\/p>

This allows trained business users, often called citizen developers, to maintain and extend processes without writing full applications from scratch.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Can business users change processes after go live?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Yes, within agreed guard rails. A common pattern is:<\/p>

- Business users adjust forms, text, and some rules<\/p>

- IT manages integration, security, and sensitive logic<\/p>

- Changes follow a simple change control and versioning process<\/p>

This keeps processes flexible while protecting key systems and data.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n How do you prevent process changes from breaking live work?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

The Versioning Framework lets you change processes safely. You can:<\/p>

- Design and test a new version<\/p>

- Move running work to a new version only when ready<\/p>

- Keep a record of changes and when they were made<\/p>

This avoids sudden breaks in live processes.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n <\/div>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Licensing and pricing<\/h4>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

How AboutFlow is licensed, priced, and what’s included in your investment<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t
\n
\n\n \n
\n
\n \n \n How is AboutFlow licensed?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Licensing is tailored around your organisation size, number of users, and the range of processes and integrations in scope.<\/p>

In a first call, we gather a clear picture of:<\/p>

- Departments and processes you want to cover<\/p>

- User counts and access patterns<\/p>

- Integration and hosting needs<\/p>

From there, we prepare a clear proposal.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Is pricing based on users, processes, or both?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Pricing structures vary by solution size. Often there is a platform fee plus a user or usage based element. In some cases, project based pricing is used for specific solutions.<\/p>

Your account team will talk through options for your case.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Are implementation services included in the licence?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Licences cover use of the platform. Design, build, integration, and change work are usually scoped as projects or service packages. This division helps you see what you are paying for in each area.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Do you offer trials?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

We normally suggest a guided demo or pilot project rather than a simple trial login. This means you see AboutFlow working on a process that matches your world, not just a blank system.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n <\/div>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Support and training<\/h4>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Ongoing assistance, documentation, and building capability within your team<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t
\n
\n\n \n
\n
\n \n \n What support do we get with AboutFlow?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Support options typically include:<\/p>

- Service desk and ticket based support

- Help with incidents and questions

- Assistance with updates and minor changes<\/p>

Service levels are agreed in writing so you know what to expect.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n What training do you provide?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Training often covers:<\/p>

- Process owners and key users

- IT support and administrators

- Citizen developers who will maintain processes<\/p>

Training combines live sessions, training manuals, and practical work in the system.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Do you have user guides and documentation?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

Yes. Projects include documentation for:<\/p>

- Process designs

- Configuration and integration setup

- User guides and manuals<\/p>

This helps with handover and internal knowledge.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n <\/div>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Evaluation and next steps<\/h4>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

How to see AboutFlow in action and start your first projectNew around here ? Start With the Basics<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t
\n
\n\n \n
\n
\n \n \n How can we see AboutFlow in action?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

The best first step is a live demo based on one of your real processes. We recommend:<\/p>

1. Book a 30 minute session<\/p>

2. Share a brief description of one problem process<\/p>

3. See how AboutFlow would support it<\/p>

You can then decide whether to move forward with a pilot or project.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n What should we prepare before the first meeting?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

It helps to have:<\/p>

- One or two processes that cause frequent pain<\/p>

- A rough idea of which systems and departments are involved<\/p>

- A few key people from IT and the business on the call<\/p>

This keeps the discussion grounded in your actual work.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n \n

\n
\n \n \n Who should attend a demo?<\/span>\n\n \n
\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n\n
\n \n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg> <\/div>\n <\/div>\n\n \n <\/a>\n <\/div>\n\n
\n\n
\n

We suggest:<\/p>

- A process owner or business lead<\/p>

- Someone from IT or architecture<\/p>

- A finance or risk representative if the process affects those areas<\/p>

This mix keeps both business and technical needs in view.<\/p> <\/div>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n <\/div>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Ready to talk about your processes?<\/h4>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

If your organisation is still running key processes on email, paper, and spreadsheets, AboutFlow can help you move to a clear, digital way of working.<\/p>

Next steps<\/strong><\/p>

Book a 30 minute demo<\/p>

See how one of your own processes would run on the AboutFlow platform.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Request a Call Back<\/h4>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

If your organisation is still running key processes on email, paper, and spreadsheets, AboutFlow can help you move to a clear, digital way of working.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t+1(888)456 780\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t<\/path><\/svg>\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\tContact Us<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

Frequently Asked Questions About AboutFlow Understanding what the platform does and how it fits your organisationNew around here ? Start With the Basics What is AboutFlow? AboutFlow is a business process management platform that lets organisations design, run, and improve process driven business applications. It replaces paper forms, email threads, and spreadsheet driven workflows with […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"elementor_header_footer","meta":{"footnotes":""},"class_list":["post-542","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.aboutflow.co.za\/index.php?rest_route=\/wp\/v2\/pages\/542","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.aboutflow.co.za\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.aboutflow.co.za\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.aboutflow.co.za\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.aboutflow.co.za\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=542"}],"version-history":[{"count":31,"href":"https:\/\/www.aboutflow.co.za\/index.php?rest_route=\/wp\/v2\/pages\/542\/revisions"}],"predecessor-version":[{"id":705,"href":"https:\/\/www.aboutflow.co.za\/index.php?rest_route=\/wp\/v2\/pages\/542\/revisions\/705"}],"wp:attachment":[{"href":"https:\/\/www.aboutflow.co.za\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=542"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}