Woub vs traditional calling: how do you capture agreements straight away?

What gets lost with traditional calling?

Usually, the conversation is not missing; the handover to the next person is. Two people can understand each other perfectly while a third still works to an old agreement. A call list shows whom you called, but does not tell your colleague which order you promised.

By traditional calling, we mean an ordinary call without configured shared records. Business telephony can also have recording and AI features. If you already have such a setup, assess the entire workflow before adding anything. For a Microsoft workspace, we cover the options separately in Woub alongside Microsoft Teams.

Illustrative example: a site manager calls about missing fixings. The construction project coordinator will ask the supplier whether Thursday is achievable. The site manager needs to know before the end of the afternoon whether the team can continue on Friday. Those are two different actions. ‘Perhaps Thursday’ is not yet a confirmed delivery date.

Anyone who only notes ‘materials Thursday’ after the conversation loses both the condition and the feedback. Anyone who captures two clear actions and informs the site manager can organise this well without AI too.

Ordinary calling and Woub side by side

The table compares an ordinary mobile call without an additional recording or AI service with the supported Woub calling route. Business telephony can also offer recording and AI through other solutions.

How to read this: ✓ = the described capability is available; × = not included as standard in this calling route. The comparison concerns an ordinary mobile call without an additional recording, AI or video service. Device- and provider-dependent capabilities are explained in the notes.

The question is therefore not how much you call. It is how many important agreements remain dependent on the memory or personal notes of whoever answers.

That problem also appears in the Karel Kamp customer story. Employees call Roland in the office or Angelo on site. According to the experience described, a summary in the project chat helps them know what the other has coordinated. This is a customer experience, rather than proof that every organisation achieves the same time saving.

For a small construction company, a simple call note may suffice provided a colleague can take over the agreements during an absence. With more projects and external parties, it becomes more important for information to be available without one person acting as intermediary. A large company also needs arrangements for access, retention and formal decision-making. Staff numbers alone do not determine the software choice.

How does a construction project coordinator call from their computer?

The construction project coordinator can start a voice or video call from the Woub project chat on their computer. The colleague on site answers through the mobile Woub app. Both use the same project-based communication, so there is no need to arrange a separate online meeting first. The Woub calling page describes this route. On first use, check the microphone, headset, camera and connection on the devices you actually use.

Calling through an account rather than only a phone number

With an ordinary call, you reach someone through their phone number. With Woub, you call a participant with a Woub account linked to a business email address or, for example, a client's personal email address. The other person needs to use the Woub app; a project invitation does not turn an ordinary mobile number into a Woub account. Invited external participants can work for free within the contractor's paid workspace and their permissions.

Group calls without merging separate phone calls

To speak to the site manager, construction project coordinator and subcontractor together, invite the Woub participants involved to a group call. This is included as standard in the calling workflow. A conference call may also be possible with ordinary mobile telephony, but you add and merge calls. Apple describes these steps and their dependence on the provider. That is a different activity from discussing together within the project workspace.

From talking to showing, including between Android and iPhone

A tradesperson can use video to show which detail, material or connection point they mean. With Woub, office and site teams use the same app for this, including when one person has Android and the other an iPhone. This keeps the discussion within the project-based conversation route instead of moving to another communication channel for video.

An ordinary voice call does not automatically provide that video workflow. FaceTime is an Apple service; an Android user can join in a browser through a received FaceTime link. Apple explains this invitation route. It is therefore incorrect to say video between Android and Apple is impossible. Woub's advantage is voice and video within the same construction project workspace, followed by supported reports and task follow-up.

The familiar call screen, with project context behind it

A Woub call can arrive on an iPhone through the normal call screen and appear in the ordinary call list, even if missed. The recipient still needs the Woub app and an internet connection. The Apple call screen does not mean Woub calls every mobile number. Woub therefore does not replace ordinary mobile telephony for contacts without the app.

A practical trial for the construction project coordinator:

1. Open the intended project. Check that the colleague on site has access to the right workspace. Use a recognisable project name, particularly with similar addresses.

2. Check the connection. Test sound, microphone and any camera with the intended equipment. A successful office call is not yet a test of the connection on site.

3. Discuss one specific action. Use the materials problem, for example. Distinguish an enquiry to the supplier from a confirmed delivery.

4. Review the outcome afterwards. Find the available conversation information and identified task. Also check whether the intended recipient can find them.

5. Let a third colleague take over. Can they determine what remains outstanding without extra explanation? That tests handover, rather than just calling.

A headset can be practical if you are looking at a drawing at the same time. The screen is mainly useful for keeping the project context to hand. During the conversation, name the relevant element and drawing revision; a conversation does not change the source document.

What if someone calls your ordinary mobile number? Treat that as a different route. Do not assume Woub automatically records the call, imports it afterwards or extracts agreements. Capture the relevant outcome within the project yourself. For recurring collaboration, agree whether the next discussion can take place through the supported project workspace.

You do not need to postpone an urgent conversation to have it in the ideal app. Arrange the necessary coordination and update the handover afterwards. If the recording or access route is unclear, use that manual approach until you have established how it works and the applicable arrangements.

What does this calling route cost, and can external participants join for free?

Woub Business includes voice and video calls, conversation recording, automatic summaries and tasks. The subscription costs €39 per administrator per month with annual billing and five users included: one administrator plus five users averages €6.50 per person per month at full occupancy. Pro costs €79 for the same user distribution, averaging €13.17, and adds the error and rework cost analyst, among other features. Check current prices, VAT and additional costs.

Invited external participants pay €0 to work within the contractor's paid Woub workspace, including project tasks and the Wouby AI workflow within their project permissions. They do not need their own paid Woub or AI subscription for this. Capabilities follow the contractor's subscription and their access; free participation does not confer general administrator rights or independent access to all Pro features.

How are supported conversations captured?

For supported recorded Woub conversations, Wouby AI creates a transcript and summary and automatically turns identified agreements into tasks. The value lies in finding and following up information; the text still needs assessment. A summary can shorten information and a transcript can misrepresent a name, dimension or trade term.

Use three checks for the materials example:

• What was said? Someone would check whether delivery on Thursday is possible.

• What is confirmed? The supplier has not yet confirmed. The delivery day remains open.

• Who needs something? The site manager expects feedback, even if the answer is negative.

Correct an error before someone orders or carries out work based on it. If the source is unclear, ask the speaker to confirm. Make the checked agreement visible and state which earlier outcome it replaces. Otherwise, an incorrect summary and a correct separate chat coexist.

One phone call about three projects

Wouby AI identifies the projects discussed and automatically links specific tasks to the right project. There is still one conversation report. If a subcontractor discusses a delivery for A, an access question for B and planning for C, the corresponding tasks can appear within their respective projects. Check project assignment and clearly name the job you are discussing during the call.

The feature for easily sharing sections of that single conversation report in other projects is still in development. Automatically allocating tasks does not mean all participants in all three projects should see the full recording. Project permissions and targeted feedback remain decisive.

In-person discussions and spoken project actions too

The built-in Woub voice recorder lets you record in-person discussions without first starting an online meeting. The recorded work discussion becomes part of the supported report and task workflow. With Wouby Actions, you can also give spoken instructions from the car to send a chat message, create a task or create a project. That is a different activity from simply dictating a message.

Woub keeps ad hoc communication around the project together. A discussed change does not thereby become an amended ERP order, updated BIM model, released DMS document or revised specialist programme. Update the relevant source according to your process. An available API likewise does not prove that transfer is already configured automatically.

How do agreements reach the people responsible?

Automatic task creation helps make an agreement visible. The right person then needs to understand what to do and when someone else is waiting for the result. Check those elements even when the task was created without manual retyping.

Follow-up for the materials conversation might look like this. This is a work example, rather than a prescribed Woub setup:

A supplier making a commitment is not automatically the internal person responsible for feedback. And ‘I will sort it’ is unclear if several participants mean different things by it. Say the names and activities explicitly. If no deadline is agreed, Woub automatically dates the task for today. That is the default follow-up date, rather than an execution timeframe agreed afterwards. The right assignee is linked automatically; check the output and amend it if the agreement meant something different.

Also distinguish between visible, understood and completed. A task's existence does not prove the site manager knows what a delay means for tomorrow. Confirm important implications directly and capture the outcome. A tick beside ‘Supplier called’ likewise does not prove the materials have arrived.

Maintain the task where your team follows up work. If you use ERP for ordering and financial processing, that process stays there. Woub can support the surrounding communication. Avoid two separately maintained versions of the same obligation without deciding which status takes priority.

First test with one construction project coordinator and one colleague on site. Then involve someone who was not part of the conversation. Count how many relevant agreements reach the next person correctly and how much remedial work is needed. Compare this with your existing call note; numbers of calls or created tasks alone say little about the result.

For the broader workflow, including updating changed agreements, read about capturing construction conversations and agreements.

What consent and privacy arrangements do you need?

Woub has established its legal framework with a specialist IT lawyer

Woub has had the legal framework for using its service documented by a specialist IT lawyer. The terms and conditions and privacy statement describe the arrangements and personal data processing. Users accept the applicable terms when creating their Woub account; the privacy statement explains how personal data is processed. You therefore do not need to draft Woub's legal basis from scratch yourself.

Users already accept the applicable Woub terms when creating their account. According to Woub, arrangements for the recording and AI workflow are included in that framework drawn up by the IT lawyer. Your team therefore does not need to set up another separate approval procedure for those documented Woub arrangements. The privacy statement describes processing. Within your organisation, apply this framework to the conversations and project permissions for which Woub is used; the European privacy regulators explain the roles of organisations and service providers.

Then choose one ordinary project agreement to trial the calling route. If a short manual follow-up works well, retain it. If agreements remain unaddressed or handover between office and site is missing, test project-based calling with Woub under appropriate conditions.

Try free for 14 days and also assess whether a colleague who was not on the call can carry out the right follow-up action.