Appfy

See all cases

Large US bank

An offer can't wait 5 days for a ticket.

At a large bank, changing an offer took 3 to 5 days: everything went through a ticket.

The problem
In a large US bank's discounts and offers programme, every new offer or change became a ticket for support, with a 3-to-5-day turnaround, because only the technical team touched the data, directly in the database. Estimate: 200 offer changes a month × 4 days of waiting ≈ 27 offers always stuck in the queue, and 200 developer hours a month at 1 hour each (changes and hours: assumptions).
What Appfy did
Appfy built the console that put campaigns in the manager's own hands: they create and change offers and upload lists in batches, and the system applies them on its own. Behind it: the screens, the part that saves the data, the number summaries and the sign-in.
The gain
The work gave the manager the ability to run campaigns in batches. No measured result is verified.

  1. Scene 1 of 7The company

    Offers in front, a queue of tickets behind.

    A large US bank runs a discounts and offers programme. Customers see the offers; behind them, every new offer or change became a ticket for support.

  2. Scene 2 of 7The problem

    Changing an offer took 3 to 5 days.

    Discounts, coupons, merchants, lists, users. Every change became a ticket for support, because only the technical team touched the data, directly in the database, and each one waited 3 to 5 days.

  3. Scene 3 of 7The goal

    The goal: managers run their own campaigns.

    Take the manager out of the queue. For that, a console with a sign-in and one area for each task: view and edit an offer, search customers and merchants, and a dashboard.

  4. Scene 4 of 7What Appfy did

    The front and the back of the console.

    Appfy did both ends: in front, the manager's screens; behind, the part that fetches the offer and saves the change, with nobody touching the data directly.

  5. Scene 5 of 7What Appfy did

    Campaigns in batches, applied on their own.

    The manager uploads a whole list at once, and the system applies it on its own, in batches. Automatic routines summarize the numbers for the dashboard, and one sign-in opens everything.

  6. Scene 6 of 7What changed

    No ticket: managers change their own campaigns.

    The work gave the manager the ability to run campaigns in batches. No measured result is verified.

  7. Scene 7 of 7And in your company?

    Does changing an offer take days? Put control in the hands of whoever decides.

    If every change to a price, offer or record becomes a ticket, Appfy builds the console so whoever decides can do it alone. Start with a free 30-minute conversation.