TechAppForce

Processes, configured. Not hand-coded.

Every approver gets one inbox. Reminders and escalation go out on their own.

Book a DemoBuild an approval workflow
My inboxIllustration
  • Purchase request: laptops for new hiresPriya S. · Operations · Manager approval
    Due today
    ApproveRejectReturn for changesDelegate
  • Vendor onboarding: new packaging supplierProcurement · Finance approval
    Overdue, escalated
  • Leave request: 3 days in OctoberArjun M. · Support · Reporting manager
    Due in 2 days
  • Discount over 15%: annual renewalSales · Sales director
    Due tomorrow
Every approval waiting for you, in one place, with the time it has left. Records stay locked while they are under approval.

The problem

Approvals live in inboxes and reply-alls.

Nobody can see where a request is, or why it was decided.

  1. Invoice from a supplierArrives by email, or in a shared spreadsheetMonday
  2. Fwd: Invoice from a supplierForwarded to whoever might approve this kind of thingTuesday
  3. Re: Fwd: Invoice from a supplierWaiting in an inbox until somebody asks where it isNext week
  4. Re: Re: Fwd: Invoice from a supplierThe decision: a reply-all nobody can findA month later
The rules live in one person's head, and change when that person leaves.

How we solve it

Draw the process once. The platform runs it.

Statuses, approval levels, time limits and follow-up work are configuration you review and release.

  1. SubmittedAccounts payable
  2. Level 1Cost centre managerApprove · return · reject
  3. Level 2Finance, above the limitApprove · reject
  4. ApprovedThen paid
Waiting too long? A reminder, then an escalation to the person you named.
Draft straight to Paid: not allowed
On approval, a workflow does the follow-up
  • Purchase order updated
  • Payments system called over HTTP
  • Clerk notified
  • Whole trail on the record

What you get

Five building blocks, all configuration

Lifecycles, approvals, workflows, notifications and schedules.

Lifecycles

Ticket lifecycle

  1. New
  2. Assigned
  3. In progress
  4. Resolved

Resolved requires a resolution note. Moving to Assigned notifies the assignee.

Read more

Define statuses and the transitions allowed between them. Records get a lifecycle when they are created, move only along allowed transitions, and keep their history with SLA fields. Validators, including your own C#, decide whether a move may happen.

Approvals

Decisions

  • Approve
  • Reject
  • Return
  • Delegate
  • Reassign
  • Recall

Each decision is stored with a snapshot of the record, chained so the history can be verified.

Read more

Choose approvers by user, role, team, reporting manager, a field on the record or a saved query. Run levels in sequence or in parallel, require any, all, N of M or a percentage, and route by amount bands. Records lock while under approval, reminders and escalation follow the SLA, and changes after approval can require re-approval.

Triggers and workflows

When   Opportunity moves to Won
1  CreateRecord   Invoice from the opportunity
2  If             Amount > 50,000
3    SendEmail    Finance director
4  HttpRequest    POST to your accounting system
5  SendInApp      Account owner
Read more

Triggers fire when records are created, edited or deleted, with field-change criteria, or on a cron schedule. Workflows chain 26 built-in actions: create and update records, run queries and stored procedures, branch and loop, call HTTP endpoints, change statuses and send notifications. Add your own actions in C#.

All workflow actions

Notifications

Channels

  • Email
  • SMS
  • Webhook
  • In-app

Push notifications are On the roadmap

Read more

Email, SMS, webhook and in-app notifications from triggers, approvals, mentions and workflows. Templates use Liquid with data from saved queries. Recipients can be addresses, the record owner, a role or a query, and each user chooses their channels.

Scheduled work

Examples

  • Every weekday 08:00Email each owner their overdue tickets
  • First of the monthExcel report of last month's orders
Read more

Schedules run workflows and reports on cron expressions or once at a set time: daily digests, month-end reports, reminders and clean-ups.

Examples you can build

Illustrated examples of apps teams build on TechAppForce, each with its records, approvals, screens and reports.

All use cases

Bring us your messiest approval process

However many inboxes and spreadsheets are involved, in a demo we configure the lifecycle, the approval levels and the reminders with you.

Start BuildingBook a DemoExplore TAF StudioBook a TAFI demo