Try Rigi24 Modules Free for 15 Days Before You Buy

Buying business software only from a feature list is risky. The important question is whether a module works inside the real workflow, whether the team can adopt it and whether it solves a specific problem. Rigi24 therefore supports a 15-Day Free Trial for paid modules: a controlled period for real evaluation before purchase.

The trial is not automatic. A Business submits a request, the request remains Pending, Super Admin reviews it and the trial starts after approval and activation for the specific Business + Module.

What is a trial supposed to prove?

The purpose is not to collect a month of free software or activate every module at the same time. A good trial should answer a business question: “Does this module create enough practical value for us to buy it?”

For example:

• Booking: does it reduce calls and messages used to arrange appointments?
• Queue: does it improve order and waiting in a physical location?
• CRM: does it reduce forgotten follow-ups and tasks?
• WebRTC: is direct web calling or softphone functionality valuable to the team?
• AI: can it handle a meaningful part of repetitive questions or response workflow?
• Store: does structured catalogue and order capture fit the business model?

When the question is defined before activation, 15 days can produce useful evidence.

Trial activation process step by step

1. The Business chooses a module

The company identifies the paid capability it wants to evaluate. Core should already provide the base Business environment.

2. A trial request is submitted

Submitting the request does not immediately activate the feature. The request enters Pending status for review.

3. Super Admin reviews the request

Rigi24 can check whether the standard trial for that Business + Module has already been used and whether an exception or additional review is required.

4. The approved trial becomes active

The real period begins when the trial is activated. The system can track timestamps such as trial_started_at and trial_ends_at so expiry is managed on the server rather than left to a browser timer.

5. The Business decides before expiry

The product should make the approaching end visible. The policy includes a near-expiry reminder, such as “your trial ends in 3 days,” together with a clear activation/purchase path.

Is a payment card required?

No. The standard trial does not require a card or an initial payment. The intention is to let the business evaluate the product itself before entering the paid subscription process.

If the business later purchases the module, the entitlement must be activated only after Rigi24 receives valid server-side payment confirmation for its own subscription/service. A front-end “success” return page alone must never grant access.

How long is the trial?

The standard duration is 15 days. When a justified evaluation needs more time, an administrator can extend the same trial so that the total period can reach up to 30 days.

The extension is an administrative decision, not an automatic right. Its purpose is to support a legitimate evaluation, not to turn a paid module into a permanently free service.

How many trials can one Business use for the same module?

The standard rule is one trial per Business + Module. If the same Business already used a normal CRM trial, another CRM trial should not be automatically granted as if it were the first one.

Admin retains an override for exceptional situations—for example, a major product change or a justified commercial reason—but an override is explicitly different from the standard policy.

Prepare before the 15 days begin

The biggest waste is activating a trial and then discovering that nobody has time to use it during the first week. Before requesting it, answer five questions:

1. Who is responsible for testing?
2. Which real workflow will be used?
3. What minimum data/configuration is required?
4. What does success look like?
5. On which day will the team review the result?

For Booking, for example, do more than create a service and look at the page. Run real or realistic bookings, test changes, review the customer experience and check the operator workflow.

A practical 15-day plan

Days 1–2: setup and orientation

Configure the module, assign the relevant users and prepare the test scenario.

Days 3–10: real usage

Use the module as part of actual work. Record questions and friction instead of abandoning the test because the interface is unfamiliar on day one.

Days 11–13: measurement

Compare with the previous process. Did the team save time? Did errors fall? Did customer or operator experience improve?

Days 14–15: decision

If the value is clear, move to paid activation. If it is not, identify why: the module may be wrong for the problem, the configuration may be wrong or the original problem may have been misunderstood.

What data should be used during a trial?

Use enough data to create a representative real-world test, but do not import a massive historical dataset before you even know whether the module will be purchased. A focused sample is often better for evaluation.

Sensitive information should follow the same access and security standards during a trial as it would in normal production. “It is only a trial” is not a reason to use shared accounts or uncontrolled data.

What happens when the trial ends?

When the period expires, the module is disabled unless paid activation has been completed. The product direction is not to instantly delete all trial data at the exact moment of expiry. However, Rigi24 has not committed to a fixed public retention promise such as 30 or 60 days for every module.

A business should therefore not assume trial data will remain indefinitely without an active entitlement. If continuity matters, make the purchase decision before the trial finishes.

Secure paid activation after the trial

The entitlement flow matters technically. A paid module must not become active just because the browser reaches a success URL. The correct logic is:

1. a Rigi24 purchase/subscription order is created;
2. the customer completes payment;
3. the backend verifies a valid payment result;
4. the module entitlement is activated server-side;
5. the UI reads the active status from the server.

This prevents accidental or manipulated front-end states from granting commercial functionality.

Trial vs free Core: they are not the same thing

Rigi24 Core is a permanent free foundation, not a 15-day trial. The Business profile, public page, one branch, up to three users, Basic Customer Directory and other Core basics do not disappear because a paid-module trial ends.

The trial applies only to paid modules. If a CRM trial expires, the Business still has its Core environment.

Should you trial several modules at once?

Usually not. If a small team activates five new systems simultaneously, it becomes difficult to learn any of them properly and nearly impossible to know which change produced a benefit.

Prioritize the biggest operational problem. If physical waiting is the major customer complaint, evaluate Queue before spending attention on AI or Store.

When is an extension reasonable?

An extension can make sense when there is a practical reason, such as:

• part of the period was lost because the business was closed;
• required configuration/integration consumed significant trial time;
• the workflow has a longer cycle and needs more observation;
• the team used the trial properly but needs a few more days of evidence.

Repeated extensions because nobody planned time to test are not the purpose of the policy.

Trial request checklist

• exact module selected;
• business problem written down;
• internal test owner assigned;
• required setup/data prepared;
• team understands the request requires approval;
• standard period understood as 15 days;
• possible extension understood as up to 30 total days at Admin discretion;
• no card required for the standard trial;
• success measure defined;
• team understands expiry disables the module.

Conclusion

A good trial reduces the risk of a purchasing decision. Rigi24 gives a business 15 days to test a paid module in a real scenario, without requiring a payment card and with an approval-based activation process.

If the Core foundation is not ready yet, complete the Rigi24 Core setup guide first. If you are unsure which module deserves priority, use Rigi24 for small businesses to identify the problem before requesting the trial.

Test the module in real work before you buy

Create your Business, start with free Core and request a 15-day trial for the module you actually need.

Start Rigi24 for free

Frequently asked questions

How long is the standard trial?

15 days, extendable with admin approval up to 30 days in total.

Do I need to pay to start the trial?

No. No payment or bank card is required to start a module trial.

Can I trial the same module more than once?

The normal rule is one trial per Business + Module; Super Admin can override it in legitimate special cases.

Is data deleted immediately when the trial ends?

No. The module is disabled; data retention follows the policy for that module.

Does free Core remain active after a trial?

Yes. Core is free and non-expiring.