Product Requests

Clear briefs.
Better player decisions.

Capture club briefs, assess your roster and keep the next action clear. Explore Community: confidential briefs shared between agencies.

Guided private beta · Access and enabled workflows confirmed before activation.

Your agency’s request desk

Know the brief. Own the next move.

Private desk
Private deskEnlarge
Requests Private desk with fictional club briefs, contacts and next actions. Northbridge FC’s centre-back brief is selected, owned by Jamie R., with a follow-up due today.

Actual product excerpt · Fictional records

The requirementA centre-back, 18–23, with a €12–18m budget.

The relationshipSam is the club contact. Jamie owns the brief.

The next stepConfirm availability before sharing a shortlist.

Capture & organise

Start with what
you know.

Log a club brief or call. Add detail as the opportunity develops.

  1. 01

    Source

    Choose the club, agent or free-agent player.

  2. 02

    Brief

    Add the position or player, then budget, profile and timing if known.

  3. 03

    Review

    Check the details and possible duplicates before saving.

Find a club or contact. Focus on priority briefs and follow-ups due.

Log request · BriefEnlarge
The actual request form’s Brief step, with Position search selected and centre-back (CB) added for fictional Northbridge FC. Enlarge to inspect the full form.

Actual product excerpt · Fictional records

Player matching

A reason behind
every name.

Choose must-haves and preferences. Assess players from your agency’s roster, then compare the evidence before making a call.

RecommendedMust-haves pass; enough evidence

Needs reviewA requirement needs confirmation

ExcludedA must-have is not met

Choose a matching example

See the fit. See what’s missing.

Luka fits the age and position. His availability and proposed fee still need confirmation.

A strong fit on known criteria can still mean Needs review.

Suggested matches · Player reviewEnlarge
Luka Petrovic needs review: his recorded position and age fit, but availability and the proposed fee need confirmation. Each missing requirement is explained.

Actual product excerpt · Fictional records

Better fit, or better evidence?

Luka fits the age range but has two open checks. Noah’s availability and €16m fee are confirmed; at 24, he misses the age preference.

Fit on known requirements shows how closely a player matches the brief. Checks completed counts requirements with a known result. Compare two or three roster players before deciding.

Suggested matches · ComparisonEnlarge

The decision in this example

Luka Petrovic 21 · Centre-back
Fit on known requirements: 100/100Checks completed: 2 of 4Age fits. Confirm availability and fee.
Noah Martins 24 · Centre-back
Fit on known requirements: 86/100Checks completed: 4 of 4Available at €16m. Outside the age preference.

Higher fit does not mean stronger evidence.

Luka, 21: fit on known requirements 100/100, 2 of 4 checks completed; availability and fee unconfirmed. Noah, 24: fit 86/100, all 4 checks completed; availability and €16m fee confirmed, but outside the preferred age range.

Actual product excerptExample summary · Enlarge for actual interface · Fictional records

Shortlists & follow-ups

Keep the next
conversation moving.

Keep the shortlist, contact history and next follow-up with the brief. Give the team enough context to pick up the conversation.

Choose a follow-through example

Keep the reasoning with the player.

Save a match or add a player from your records. Keep your notes and any checks still needed alongside each name.

“Mark shortlist shared” records a shortlist you have already sent outside Entekka. It does not send a message.

Private desk · ShortlistEnlarge
Luka Petrovic saved to Northbridge’s shortlist with agent notes to confirm availability. Mark shortlist shared records external sharing.

Actual product excerpt · Fictional records

Leave a clear next step.

Sam confirms Northbridge’s budget. Jamie records the call and sets 18 July to check availability before sharing the shortlist.

The saved call and next date stay on the brief. It returns to the follow-up queue when due.

Private desk · Recorded callEnlarge
Saved call with Sam Wilson at Northbridge FC on 16 July. Budget confirmed at €12–18m; Jamie will check Luka’s availability. The next follow-up is 18 July.

Actual product excerpt · Fictional records

Put it into practice: build a shortlist
Community pool

A wider network.
Clear boundaries.

Explore another agency’s brief and speak with the listing agent. Publish your own only when you choose to share it.

Choose a community example

Share the need. Protect the source.

See the position, budget and timing, plus the listing agent and agency. Start an enquiry when you have a relevant player or question.

The outside-agency view hides the club, source contact, private notes and other agencies’ conversations.

Community pool · Outside agency viewEnlarge
Confidential centre-back recruitment brief with England, Premier Division, age 18–23 and a €12–18m budget. Morgan L. at Westhaven Agency is the listing agent; club and source contact are hidden.

Actual product excerpt · Fictional records

Every conversation has its brief.

Keep replies attached to the brief. See who needs an answer and bring the right teammates into the conversation.

Only the people involved can see the conversation. Workspace membership alone does not grant access.

Community pool · MessagesEnlarge
A fictional conversation with Westhaven Agency stays attached to its centre-back brief. The agents discuss a permanent move and confirm availability and fees before a recommendation.

Actual product excerpt · Fictional records

Shared on purpose. Private desk briefs are not automatically published to Community.

Access confirmed at rollout. Community requests are included in Pro. Availability is confirmed before activation.

A clear brief makes the next move easier.

Check the player’s profile and club context, then progress a promising conversation through the appropriate pipeline.

Questions about Requests.

Does a private request automatically become public?

No. Private requests and community briefs are distinct. Sharing a community brief is a deliberate action, with private source details kept out of the shared presentation.

Which players do suggested matches assess?

Suggested matches assess players in your agency’s roster against the brief. Review must-haves, preferences and the available evidence; this is not a search of every player on the market.

Does a strong fit mean a player is available?

No. Fit on known requirements shows how closely a player matches the brief. Checks completed counts requirements with a known result. Availability or another must-have can still be unconfirmed, so a strong fit can still need review.

Does marking a shortlist shared send it to the club?

No. It records that you have shared the shortlist outside Entekka. Keep notes and follow-ups with the brief so the team knows what happened and what comes next.

Who can see Community conversations?

Conversations are limited to their participants. Outside agencies see the published brief and listing agent, not the private club, source contact, internal notes or other agencies’ conversations. Community requests are included in Pro; access and enabled workflows are confirmed during rollout.

Bring a brief. See the next steps.

Walk through capture, matching and follow-up with our team. We’ll confirm the workflows and Community access available to your agency.

Request a demo

Arrange a guided walkthrough by email.