Skip to main content

A 40% reduction in the credit release SLA: lessons from Ademicon

  • Nov 19, 2026 12:49 PM UTC
  • 0 replies
  • 2 views
vinicius.pereira
Community Manager

👤 For credit operations teams and people who manage approval processes
🔐 Using these resources depends on your company’s plan, enabled features, and permissions
🎯 To find where requests stall and test an improvement in your pipe

 

Inside the process

A customer asks when their credit will be released. The team checks the latest message and still has to find out whether the request is waiting for a document, a review, or someone to pick it up.

At Ademicon, connecting credit release workflows in Pipefy gave the team visibility from start to finish. The case study reports a 40% reduction in the credit release SLA.

By the end of this article, you’ll know what to record when a request moves between teams, how to test that handoff with the people who do the work, and how to investigate delays.

 

What you will learn:

 

Record what the next team needs

Ademicon relied on email, and the work was spread across separate workflows. That made requests harder to track. The team connected its workflows in Pipefy and automated critical activities so it could follow each stage of credit release.

Imagine that in your process, one person finishes checking the documents and someone else reviews the request. The reviewer needs to know what was checked, whether anything is outstanding, and who is handling it. If that information still lives in a conversation, record the outcome of the document check with the request before passing it along.

In Pipefy, each card represents a request, and phases represent the stages of the process. To see whether the handoff was recorded, check the card Timeline. It shows when a phase or field changed and who or what triggered the change.

 

Test handoffs with the people who do the work

Ademicon’s team built 95% of the workflow itself without writing code. During implementation, the team tested and refined the workflow directly with the people who used it.

Ask the people who submit and receive requests to run through the same test. Try a complete request and one with a missing document. For the second request, see whether the reviewer can record what’s missing and whether the person who needs to address it knows how to send the request back for review.

In your pipe, use a test card to see how the request shows up in the next phase and what information is available there. If the test shows that the issue began at intake, use How to test your form before sharing it to choose scenarios to check.

 

Investigate where requests wait

Once the team could see the whole workflow, Ademicon could follow each stage and identify where the process could improve.

The service level agreement (SLA) sets the expected time for credit release. To understand why it’s at risk, look at which phase requests get stuck in. If the team often waits for the requester to provide a document, test a clearer way to explain what’s missing and agree on who will check for a reply.

To agree on a time limit and decide who acts when it’s exceeded, read Phase SLAs in Pipefy to keep deadlines on track.

Ademicon’s CTO describes what this visibility made possible:

 

“Pipefy helps us see where we’re wasting time and what we can do differently.”

André Carrera, CTO at Ademicon

 

Apply this analysis to your pipe

Choose a recurring request and follow it through to completion. At each handoff, note what was checked, who receives the request, and who handles discrepancies. If the next person still has to look elsewhere for information, choose one piece of information to record on the card.

Test the change with the people who submit and receive the request. Compare requests of the same type before and after the change. If incomplete information was the issue, track how many requests were sent back for that reason.

 

Continue with Pipefy Academy

The Pipefy Process Manager Certification covers how to use forms, connections, and reports to track your process.

 

Before moving on, confirm that you understand:

☐ What the next team needs to find in the request.

☐ How to test a complete request and one with missing information.

☐ Which delay you want to investigate and how you’ll track the effect of the change.

 

Make credit release easier to track with lessons from Ademicon

Does your team have to search through several conversations to find out where a request stalled? Talk to Pipefy about how to connect stages and track requests at your company.

Explore what’s possible for your process

 

Read the full Ademicon success story from Pipefy.