Keepface
Sign up

Tasks, points and approvals

A task is an action a customer takes (follow, share, tag, engage, review) for a fixed number of points, verified automatically or approved by you in the Approvals queue.

Tasks are the engine of Customer Advocacy. A customer does something small, the action gets verified, points land in their balance, and those points buy something from your rewards catalog.

Anatomy of a task

FieldWhat it does
Categoryfollow, share, tag, engage, review, or other
PlatformInstagram, TikTok, YouTube, Facebook, X, LinkedIn, Threads, Telegram, Google Maps, Trustpilot, App Store, Play Store, or anywhere
VerificationHow completion is proven (see below)
Reward points0 to 50,000 per completion
Target URL or handleThe post to act on, or the handle auto-verification checks for
BudgetOptional total points cap for the whole task

Three ways to start a task

  1. Clone from the library. Open Tasks then Templates and pick from the starter library. The row is copied into your workspace, so tuning the reward or the copy never affects the shared library.
  2. Build your own. The builder walks category, platform, verification and points, and suggests a title as you go (“Follow us on Instagram”).
  3. Edit an existing one. Any workspace task can be reopened and retuned.

Verification methods

MethodWho does the work
Proof link (self_declared)The customer pastes a link. It lands in Approvals and pays only after you approve.
I mark it done myself (admin_manual)No submission at all. You award completions by hand, which fits events and offline actions.
My system confirms it (webhook)Your backend calls the Keepface verify webhook when the action happens. Set the signing secret up under Settings then Webhooks.
Connected account (oauth_check)Checked through the customer’s connected social account. Points land instantly.
Platform check (api_poll)Keepface looks for the action on the platform and awards when it finds it.
Telegram bot (bot_deeplink)The @keepface_bot confirms it, including channel membership where the task asks for it.

The builder offers the first three, because they need nothing beyond your own workspace. The auto-verified methods come pre-set on library templates that need them.

The Approvals queue

Tasks then Approvals is a cross-template feed of everything sitting in submitted. Each row shows the customer, the task, the proof link and the points at stake. Approve pays the points (with the member’s tier multiplier applied) and writes the completion; reject closes it with a reason.

Approval is atomic and idempotent, so a double tap cannot pay twice.

Guardrails

  • Monthly emission cap: the most points the workspace can mint in a calendar month. Once hit, approvals and grants soft-fail until the next month or until you raise it.
  • Per-task budget enforcement: when on, a task refuses approvals after its own budget is spent. Leave it off during a pilot.
  • Emergency stop: a kill switch that blocks approvals, redemptions and grants while you investigate. Read endpoints stay live.

All three live on Settings then Governance.

Frequently asked questions

Do I have to write tasks from scratch?

No. There is a starter library of ready-made templates you can clone in one click, and cloning copies the row into your workspace so your edits never touch the library.

What stops a customer from claiming a task they did not do?

The verification method. Proof-link tasks land in your Approvals queue and pay nothing until you approve. Auto-verified methods confirm the action on the platform or through your own backend.

Can I cap what a task costs me?

Yes. Each task can carry a total points budget, and Settings then Governance has a per-task budget switch plus a workspace-wide monthly emission cap.

How fast are submissions checked?

A sweep runs every ten minutes over submitted assignments and dispatches the verifier for each one. Anything it cannot decide stays in Approvals.

What happens to points once earned?

They land in the member's points ledger, feed their tier score, and can be spent in your rewards catalog.

Was this article helpful?