{ "schemaVersion": "1.0.0", "schema": "https://hivesilo.com/evidence/company-fact-sheet.schema.json", "slug": "resrequest", "product": "ResRequest", "url": "https://hivesilo.com/integrations/resrequest", "title": "ResRequest Integration for Safari Booking Options | HiveSilo", "description": "Review an expiring safari option against an agency agreement and camp contribution. See which ResRequest access is agent-specific and what needs a separate reporting agreement.", "reviewed": "2026-11-04", "connectionStatus": "proposed", "image": { "width": 1800, "height": 1195, "group": "expedition", "alt": "Illustrative expedition arrival setting for the ResRequest integration workflow", "heroVariants": [ { "path": "/img/integrations/resrequest-integration-expedition-480.57bf201a3725.webp", "width": 480, "height": 319, "bytes": 33568 }, { "path": "/img/integrations/resrequest-integration-expedition-768.ed12cc0598f8.webp", "width": 768, "height": 510, "bytes": 77226 }, { "path": "/img/integrations/resrequest-integration-expedition-1200.0ccfe75da8e4.webp", "width": 1200, "height": 797, "bytes": 162014 }, { "path": "/img/integrations/resrequest-integration-expedition-1800.8f014574ef38.webp", "width": 1800, "height": 1195, "bytes": 265904 } ], "socialImage": { "path": "/og/resrequest-integration-intelligence.3e12b7e28118.png", "width": 1200, "height": 630, "bytes": 923929 }, "retiredSocialImages": [], "sourceSha256": "768f74da8238", "source": "AI-generated illustrative scene; not a vendor or customer facility", "illustrative": true }, "content": { "inventoryId": "P604", "slug": "resrequest", "product": "ResRequest", "niche": "outfitters-expeditions", "reviewed": "2026-11-04", "contentVersion": "1.0.0", "title": "ResRequest Integration for Safari Booking Options | HiveSilo", "description": "Review an expiring safari option against an agency agreement and camp contribution. See which ResRequest access is agent-specific and what needs a separate reporting agreement.", "primaryKeyword": "ResRequest integration", "secondaryKeywords": [ "ResRequest Enterprise", "ResConnect API", "ResRequest safari reservations" ], "hero": { "h1": "Which safari option in ResRequest needs a decision today?", "lede": "A private group wants to add a second camp, but its first provisional hold is about to expire. The operator needs to know what the agent was promised, which nights still have value, and who can extend the option. HiveSilo can prepare that review for the safari sales team.", "imageLines": [ "Two camps.", "One itinerary to confirm." ] }, "problem": { "heading": "The first camp’s hold may expire before the second confirms.", "summary": "Review the operator’s promise across the itinerary before releasing or extending space.", "question": "Can the reservations manager protect the booking without displacing higher-value business?", "paragraphs": [ "Asilia Lodges and Camps runs a public reservation front door powered by ResRequest. Asilia Africa describes 18 camps and lodges across Kenya, Tanzania and Uganda and a workforce of more than 1,000. Its booking terms explain how provisional reservations may be held and released. Its public login is evidence of product use, not authorization to enter a customer account.", "A provisional room at one camp can be commercially valuable only if the surrounding itinerary works. The agent’s guarantee, the operator’s approved release date and a replacement group’s fit may live in separate records. Compare the obligations for the whole stay before asking a specialist to extend an option or quote an alternative." ] }, "value": { "heading": "Make the option decision accountable across camps.", "summary": "Identify the sales owner who can verify a private group’s status, compare the cost of holding nights and decide what the agent should hear.", "decisions": [ { "title": "Which hold matters first?", "body": "Compare the option expiry, affected camp nights and agent’s agreement with the current reservation record." }, { "title": "What would an extension cost?", "body": "Review approved camp contribution, agent commission, cancellations and alternative demand before extending a hold." }, { "title": "Who can confirm the itinerary?", "body": "Give the accountable safari specialist a decision; they verify inventory and approve any offer or release." } ], "capabilities": [ { "heading": "Identify the threatened stay.", "body": "If ResRequest expressly authorizes the required use, relate the permitted status to the operator’s own multi-camp itinerary and agency agreement inside the approved environment. A booking visible to one agent cannot be assumed visible to another.", "output": "An option review with dates, unresolved commitments and an accountable owner.", "sourceIds": [ "RR1", "RR2" ] }, { "heading": "Recover a booking the operator owns.", "body": "Revenue Seeker can revisit a separately authorized direct enquiry after the agent confirms an option release. Use the operator’s own enquiry and permission; suppress duplicates and protected partner business.", "output": "An eligible group request for the safari sales specialist.", "sourceIds": [] }, { "heading": "Measure the realized itinerary.", "body": "Reconcile completed stays and actual receipts across the itinerary. Deduct partner commission, cancellations, concessions and internal transfers between camps. Credit an additional booking only when comparison with normal handling supports it.", "output": "Net itinerary contribution after shared costs.", "sourceIds": [] } ] }, "example": { "heading": "A two-camp itinerary with different release dates.", "setup": "Illustrative example. An agent holds three nights at the first camp. A private group needs a second camp to confirm before it can accept the itinerary. The first option expires tomorrow.", "nativeBaseline": "ResRequest Enterprise supports reservations, CRM, multi-property distribution and reporting. Authorized agents can access only inventory and reservations granted to their role.", "inputs": [ "The operator’s provisional itinerary, option dates and contractually permitted agent context.", "Current camp status verified by the authorized reservations team.", "Approved account-level contribution assumptions and the private group’s commercial conditions." ], "decision": "Should the operator request a short extension, offer different dates, or release the first camp?", "output": "The sales specialist receives the first expiry and the missing second-camp confirmation. They confirm availability, authority and partner conditions before notifying the agent. Until then, the proposed itinerary stays provisional.", "owner": "Safari sales specialist, with the camp reservations manager authorizing inventory changes.", "hold": "Wait when availability is stale, the agent allocation excludes a camp, a provisional option has expired or the request could expose another guest or third-party inventory.", "record": "Reconcile the completed itinerary, commission and margin across camps. Reservations, passenger manifests and identified supplier contracts remain in the operator’s systems.", "sourceIds": [ "RR1", "RR2", "RR3", "RR6" ] }, "governance": { "intro": "The operator controls inventory and agency terms. A commercial review cannot release rooms, extend provisional dates or make safari safety decisions.", "example": "Route a dated hold question to the safari reservations manager. The manager verifies each camp and authorizes communication or action through the approved booking process." }, "privacy": { "intro": "Retain guest identities, detailed movements, agents’ confidential terms and camp allocations inside the operator’s approved environment.", "detail": "ResRequest requires a direct agreement for a third party to use API data. It prohibits downstream sharing without prior written agreement and bars AI training, improvement and associated derived datasets unless expressly agreed in writing. Keep ResRequest data out of cross-client learning, ad targeting and model evaluation. Use the operator’s independently authorized enquiry records when this permission is absent." }, "outcomes": { "intro": "Measure completed coherent itineraries, avoided premature releases and net receipts after commissions. Compare with similar camp combinations and seasonality.", "panels": [ "Prioritize the group itinerary whose first option is about to expire.", "Recognize independently authorized relationships with repeat safari groups.", "Compare the operator’s eligible direct and agent channels after commissions.", "Filter invalid marketing enquiries from genuine group requests.", "Revisit a first-party group opportunity after a documented option release." ] }, "fit": { "intro": "For safari operators with multiple camps or properties, a meaningful mix of direct and agent bookings, and repeated provisional-hold decisions.", "good": [ "The reservations team can verify status at each camp.", "An agency agreement defines the commercial rights for the itinerary.", "The operator can reconcile earned revenue across camps and bookings." ], "consider": [ "ResRequest Enterprise reporting may already resolve a single-camp allocation question.", "A normal ResConnect agent account does not confer extended reporting, third-party delivery or AI-processing rights." ] }, "connection": { "heading": "Determine which ResRequest agreement covers the workflow.", "paragraphs": [ "The ResConnect partner programme is for approved agent commerce and booking. Its reservation lookup returns only reservations linked to the agent assigned to the API user. Inventory access, rates and allocations depend on the configured role and property. That agent path cannot be repurposed as an operator-wide opportunity feed.", "ResRequest separately reviews extended uses. Its Big Data reporting service supports approved reporting and business intelligence under distinct governance, fees and usage terms. A third-party platform needs the appropriate direct agreement; forwarding an agent export, even after removing names, is not a substitute.", "With no agreed ResRequest route, keep its booking records in the vendor system. An authorized operator can separately use its own enquiry, agreement and finance records for a commercial review; mark any unverified camp status unknown." ], "sourceIds": [ "RR1", "RR2", "RR3" ] }, "faqs": [ { "question": "Where is ResRequest used in a luxury safari operation?", "answer": "Asilia Lodges and Camps’ branded public reservations front door identifies ResRequest. The operator describes 18 camps and lodges across three East African countries and more than 1,000 employees. That is evidence of a substantial named operation, not its revenue, enterprise-wide module use or a HiveSilo relationship.", "sourceIds": [ "RR4", "RR5" ] }, { "question": "What can a ResConnect agent actually read?", "answer": "ResRequest’s reservation lookup restricts results to the agent configured for the API user. Rate and availability access depend on allocations, property and role. A partner cannot infer permission to read all competing agents or all properties from its ability to book one itinerary.", "sourceIds": [ "RR1", "RR2" ] }, { "question": "Does ResRequest offer operator-side reporting access?", "answer": "Yes. Enterprise has native reporting, and the API documentation describes a separately governed and billed Big Data service for reporting and business intelligence. Confirm commercial approval, exact objects, purpose, recipient and retention. A publicly documented service is not proof of a customer grant.", "sourceIds": [ "RR1", "RR3" ] }, { "question": "Can a ResConnect partner pass records on to HiveSilo?", "answer": "ResRequest requires prior written agreement for downstream sharing and the appropriate direct agreement for the receiving third party. A reseller’s existing access or a downloadable report does not authorize another recipient. Until approved, use independently authorized operator records only.", "sourceIds": [ "RR1" ] }, { "question": "Can ResRequest data train a model or improve shared intelligence?", "answer": "The vendor requires express written agreement for AI or machine-learning training, development or improvement, including related derived datasets. The guide excludes these uses and external advertising. Keep the records and identifying details inside their approved environment.", "sourceIds": [ "RR1" ] }, { "question": "Who decides whether the camp can extend an option?", "answer": "The operator’s authorized sales and reservations teams verify current stock, agent rights, provisional deadlines and any additional approvals. The commercial review flags the timing issue; it does not change inventory, confirm a guest stay or approve operational safety.", "sourceIds": [ "RR2", "RR6" ] }, { "question": "How would an operator measure value?", "answer": "Follow the full itinerary from confirmed option to completed nights and realized receipts. Include commission, reversals, concessions and the cost of displaced inventory. Compare equivalent camp combinations and seasons. A longer hold alone is not an improvement.", "sourceIds": [] }, { "question": "What belongs in the first briefing?", "answer": "Use an anonymized two-camp option, the documented release dates and the person who owns that decision. Bring the summary of the applicable vendor agreement. Exclude guest names, travel details, credentials and copied booking extracts.", "sourceIds": [ "RR1" ] } ], "sources": [ { "id": "RR1", "title": "ResRequest API scope, governance and data use", "url": "https://support.resrequest.com/developer/resrequest-api/", "supports": "Separates agent commerce from extended Big Data reporting; required direct agreement and explicit restrictions on third-party sharing and AI use.", "reviewed": "2026-11-04" }, { "id": "RR2", "title": "ResRequest reservation lookup", "url": "https://support.resrequest.com/developer/rv_get_reservation/", "supports": "Only reservations linked to the agent set up for the API user are returned.", "reviewed": "2026-11-04" }, { "id": "RR3", "title": "ResRequest Enterprise", "url": "https://resrequest.com/resrequest-enterprise/", "supports": "Native central reservations, property management, CRM and reporting.", "reviewed": "2026-11-04" }, { "id": "RR4", "title": "Asilia Lodges and Camps reservations", "url": "https://asilia.resrequest.com/", "supports": "Named public ResRequest-powered operator reservation entry; no authenticated access.", "reviewed": "2026-11-04" }, { "id": "RR5", "title": "Asilia Africa company profile", "url": "https://www.asiliaafrica.com/about-us/", "supports": "Operator reports 18 camps and lodges and more than 1,000 employees across three countries.", "reviewed": "2026-11-04" }, { "id": "RR6", "title": "Asilia Africa booking terms", "url": "https://www.asiliaafrica.com/booking-terms-and-conditions/", "supports": "Operator defines provisional booking, confirmation and release terms; the example on this page is illustrative.", "reviewed": "2026-11-04" } ], "relationshipContext": { "privacyContext": "The safari operator retains guest identity, movements and agent contracts. Only the expressly approved role, purpose and recipient may process ResRequest records. Do not transfer data via an agent report or derive learning data without written permission.", "diagramLabels": [ "Guest, camp and agency identities stay operator-controlled", "Only expressly approved status and option evidence", "Safari sales and reservations confirm the next step" ], "reviewIntentSentences": [ "ResRequest Enterprise already supports central reservations, property management, customer relationships and reporting.", "A ResRequest API review must distinguish the agent’s own reservation lookup from separately approved operator reporting and downstream processing.", "The commercial owner decides whether the full itinerary merits an extension after both camps verify their provisional holds." ], "sourceIds": [ "RR1", "RR2", "RR3", "RR6" ] } }, "shared": { "privacyModel": "Customer identities and re-identifiable data stay in the customer-controlled environment; only permitted non-PII signals and scores cross the configured boundary. Account, billing and support records are separate.", "governanceSteps": [ { "title": "Request", "detail": "An AI proposes an action" }, { "title": "Check", "detail": "Policy and authority" }, { "title": "Approve", "detail": "Named owner, when required" }, { "title": "Act", "detail": "Within permitted scope" }, { "title": "Record", "detail": "Keep the action, outcome and accountable owner traceable." } ], "outcomes": [ { "value": "3,790", "prefix": "", "suffix": "of 5,000", "label": "UHNW buyer score", "note": "Illustrative score" }, { "value": "4–6×", "prefix": "", "suffix": "", "label": "Reported conversion lift", "note": "Closed-revenue outcomes" }, { "value": "31%", "prefix": "Up to", "suffix": "", "label": "Reported ad-spend savings", "note": "Bot and invalid-traffic filtering" }, { "value": "99.9999%", "prefix": "", "suffix": "", "label": "Bot detection", "note": "Observed client results" }, { "value": "5–21%", "prefix": "", "suffix": "", "label": "Revenue lift from existing data", "note": "HiveSilo-reported client results" } ], "outcomeContext": "Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary.", "botDetectionGoal": "99.9999999% is a goal, not an achieved result." }, "sources": [ { "id": "RR1", "title": "ResRequest API scope, governance and data use", "url": "https://support.resrequest.com/developer/resrequest-api/", "supports": "Separates agent commerce from extended Big Data reporting; required direct agreement and explicit restrictions on third-party sharing and AI use.", "reviewed": "2026-11-04" }, { "id": "RR2", "title": "ResRequest reservation lookup", "url": "https://support.resrequest.com/developer/rv_get_reservation/", "supports": "Only reservations linked to the agent set up for the API user are returned.", "reviewed": "2026-11-04" }, { "id": "RR3", "title": "ResRequest Enterprise", "url": "https://resrequest.com/resrequest-enterprise/", "supports": "Native central reservations, property management, CRM and reporting.", "reviewed": "2026-11-04" }, { "id": "RR4", "title": "Asilia Lodges and Camps reservations", "url": "https://asilia.resrequest.com/", "supports": "Named public ResRequest-powered operator reservation entry; no authenticated access.", "reviewed": "2026-11-04" }, { "id": "RR5", "title": "Asilia Africa company profile", "url": "https://www.asiliaafrica.com/about-us/", "supports": "Operator reports 18 camps and lodges and more than 1,000 employees across three countries.", "reviewed": "2026-11-04" }, { "id": "RR6", "title": "Asilia Africa booking terms", "url": "https://www.asiliaafrica.com/booking-terms-and-conditions/", "supports": "Operator defines provisional booking, confirmation and release terms; the example on this page is illustrative.", "reviewed": "2026-11-04" }, { "id": "HS0", "title": "HiveSilo: industry coverage", "url": "https://hivesilo.com", "supports": "First-party description of buyer intelligence across 12 luxury niches.", "reviewed": "2026-10-25" }, { "id": "HS1", "title": "HiveSilo: platform", "url": "https://hivesilo.com/platform", "supports": "Published intent, sales-prioritization and traffic-quality capabilities.", "reviewed": "2026-10-25" }, { "id": "HS2", "title": "HiveSilo: integration scope", "url": "https://hivesilo.com/integrations", "supports": "Named destinations, scoped activation and customer-controlled dispatch.", "reviewed": "2026-10-25" }, { "id": "HS3", "title": "HiveSilo: security architecture", "url": "https://hivesilo.com/security-architecture", "supports": "Documented confidential processing, BYOK and customer control.", "reviewed": "2026-10-25" }, { "id": "HS4", "title": "HiveSilo: data handling", "url": "https://hivesilo.com/data-handling", "supports": "Customer identity custody, pseudonymous-data boundaries and separate account records.", "reviewed": "2026-10-25" }, { "id": "HS5", "title": "HiveSilo: published outcomes", "url": "https://hivesilo.com/case-studies", "supports": "Existing first-party outcomes material, with client-reported and illustrative descriptions.", "reviewed": "2026-10-25" }, { "id": "HS6", "title": "HiveSilo: AI agentic governance", "url": "https://hivesilo.com/ai-agentic-governance", "supports": "Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts.", "reviewed": "2026-10-25" }, { "id": "HS7", "title": "HiveSilo: AI implementation layer", "url": "https://hivesilo.com/ai-implementation-layer", "supports": "Published combined implementation model for intelligence, confidential processing and AI governance.", "reviewed": "2026-10-25" }, { "id": "HS8", "title": "HiveSilo: bot-detection results and buyer-score specimen", "url": "https://hivesilo.com/", "supports": "The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen.", "reviewed": "2026-10-25" }, { "id": "HS9", "title": "HiveSilo: owned-data revenue result briefing", "url": "https://hivesilo.com/contact", "supports": "HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows on 25 October 2026.", "reviewed": "2026-10-25" }, { "id": "HS10", "title": "HiveSilo: enterprise agreements and responsibility", "url": "https://hivesilo.com/terms", "supports": "Signed enterprise agreements govern the engagement and take precedence over website summaries.", "reviewed": "2026-10-26" } ], "articleText": "Enterprise outfitters & expeditions ResRequest + HiveSilo View scope HiveSilo / Integrations / ResRequest Which safari option in ResRequest needs a decision today? A private group wants to add a second camp, but its first provisional hold is about to expire. The operator needs to know what the agent was promised, which nights still have value, and who can extend the option. HiveSilo can prepare that review for the safari sales team. Contact HiveSilo Explore the fit Start with a conversation. No client records needed. Two camps. One itinerary to confirm. Your client list stays yours. The value AI control Your data What you could gain Let’s talk FAQs & evidence The first camp’s hold may expire before the second confirms. Review the operator’s promise across the itinerary before releasing or extending space. Can the reservations manager protect the booking without displacing higher-value business? Asilia Lodges and Camps runs a public reservation front door powered by ResRequest. Asilia Africa describes 18 camps and lodges across Kenya, Tanzania and Uganda and a workforce of more than 1,000. Its booking terms explain how provisional reservations may be held and released. Its public login is evidence of product use, not authorization to enter a customer account. A provisional room at one camp can be commercially valuable only if the surrounding itinerary works. The agent’s guarantee, the operator’s approved release date and a replacement group’s fit may live in separate records. Compare the obligations for the whole stay before asking a specialist to extend an option or quote an alternative. ResRequest Enterprise already supports central reservations, property management, customer relationships and reporting. [RR1] [RR2] [RR3] [RR6] Make the option decision accountable across camps. Identify the sales owner who can verify a private group’s status, compare the cost of holding nights and decide what the agent should hear. Talk through your use case Which hold matters first? Compare the option expiry, affected camp nights and agent’s agreement with the current reservation record. What would an extension cost? Review approved camp contribution, agent commission, cancellations and alternative demand before extending a hold. Who can confirm the itinerary? Give the accountable safari specialist a decision; they verify inventory and approve any offer or release. See the intelligence behind the next move Identify the threatened stay. If ResRequest expressly authorizes the required use, relate the permitted status to the operator’s own multi-camp itinerary and agency agreement inside the approved environment. A booking visible to one agent cannot be assumed visible to another. [RR1] [RR2] Useful output: An option review with dates, unresolved commitments and an accountable owner. Recover a booking the operator owns. Revenue Seeker can revisit a separately authorized direct enquiry after the agent confirms an option release. Use the operator’s own enquiry and permission; suppress duplicates and protected partner business. Useful output: An eligible group request for the safari sales specialist. Measure the realized itinerary. Reconcile completed stays and actual receipts across the itinerary. Deduct partner commission, cancellations, concessions and internal transfers between camps. Credit an additional booking only when comparison with normal handling supports it. Useful output: Net itinerary contribution after shared costs. A two-camp itinerary with different release dates. Illustrative example. An agent holds three nights at the first camp. A private group needs a second camp to confirm before it can accept the itinerary. The first option expires tomorrow. Start with ResRequest ResRequest Enterprise supports reservations, CRM, multi-property distribution and reporting. Authorized agents can access only inventory and reservations granted to their role. Bring the relevant context together The operator’s provisional itinerary, option dates and contractually permitted agent context. Current camp status verified by the authorized reservations team. Approved account-level contribution assumptions and the private group’s commercial conditions. Make the decision Should the operator request a short extension, offer different dates, or release the first camp? A useful output The sales specialist receives the first expiry and the missing second-camp confirmation. They confirm availability, authority and partner conditions before notifying the agent. Until then, the proposed itinerary stays provisional. Keep responsibility clear Safari sales specialist, with the camp reservations manager authorizing inventory changes. Hold and ask Wait when availability is stale, the agent allocation excludes a camp, a provisional option has expired or the request could expose another guest or third-party inventory. Record the outcome Reconcile the completed itinerary, commission and margin across camps. Reservations, passenger manifests and identified supplier contracts remain in the operator’s systems. [RR1] [RR2] [RR3] [RR6] Require control before AI acts. The operator controls inventory and agency terms. A commercial review cannot release rooms, extend provisional dates or make safari safety decisions. Route a dated hold question to the safari reservations manager. The manager verifies each camp and authorizes communication or action through the approved booking process. 1 Request An AI proposes an action 2 Check Policy and authority 3 Approve Named owner, when required 4 Act Within permitted scope 5 Record Keep the action, outcome and accountable owner traceable. Unclear authority? Hold the action. Resolve with the named, authorized owner before proceeding. Controls apply to actions routed through the configured HiveSilo boundary. Read the governance and escalation requirements Make accountable authorization a condition of putting AI to work. HiveSilo describes an operating layer that combines buyer intelligence, customer-data privacy and governance. Your deployment should establish the responsible owner and permitted scope before an agent can change records, contact buyers or trigger campaigns. HiveSilo documents policy checks before execution, default denial when authorization is unclear, human checkpoints, scoped stop controls and decision receipts. These controls apply to actions routed through its policy boundary. Keep decisions, required approvals and held actions traceable as the workflow progresses, then record the action, outcome and accountable owner. [HS6] [HS7] Who Identify the acting agent or person and name the business owner accountable for this workflow. What Define the action and permitted data categories before execution. Where Specify the approved system, destination and customer custody boundary. How Require an approved execution path, access scope and applicable policy checks. When Set the permitted conditions and approval validity; recheck authority before a held action resumes. Why Record the business purpose and the basis for allowing, denying or holding the action. An edge case should stop the affected action. For the deployment, require unresolved authority, an unapproved destination or an out-of-policy action to remain on hold. A timeout or unanswered approval request must not become permission to proceed. Who gets the question? Agree a named owner and authorized delegate for each workflow. A proposed responsibility model is: sales for buyer outreach and lead handling; marketing for campaign spend and audiences; security or privacy for data-access exceptions; the platform owner for connector or runtime changes. Test the escalation route. If no authorized reviewer is available, keep the action held. Named-owner routing is configured and demonstrated for each deployment. Governance covers actions routed through its configured boundary; external systems remain responsible for actions outside that scope. Make responsibility part of the AI rollout. Use the AI implementation layer to put policy checks, approval checkpoints and decision records around the actions in scope. Your enterprise agreement defines the legal responsibilities and any agreed liability allocation or transfer. [HS7] [HS10] Explore the AI implementation layer · How enterprise agreements govern the engagement Your client list stays yours. Retain guest identities, detailed movements, agents’ confidential terms and camp allocations inside the operator’s approved environment. Explore the security architecture Your client records stay with your business under HiveSilo’s published architecture. How your data stays under your control The safari operator retains guest identity, movements and agent contracts. Only the expressly approved role, purpose and recipient may process ResRequest records. Do not transfer data via an agent report or derive learning data without written permission. [RR1] [RR2] [RR3] [RR6] [HS4] Your controlled environment Guest, camp and agency identities stay operator-controlled Identities and re-identifiable records stay here. Your enclave. Your keys. Only permitted non-PII signals and scores Only expressly approved status and option evidence HiveSilo intelligence Safari sales and reservations confirm the next step No customer identity transfer to HiveSilo. Published architecture. Confirm the data boundary for your deployment. Customer-controlled keys Documented BYOK options cover AWS, Azure and GCP. Review key ownership, revocation and the deployment's access policy with your security team. [HS3] Protected processing The architecture describes confidential computing and trusted execution environments. Request deployment-specific attestation and data-flow evidence for your CISO's review. [HS3] Scoped destinations and actions Agree which systems receive outputs and what actions are authorized. Keep identity handling within the documented customer boundary. [HS2] [HS4] Control through the full relationship Review permitted use, export, retention, deletion and offboarding terms. Customer-controlled keys are one control; they do not establish every contractual exit right. [HS3] [HS4] ResRequest requires a direct agreement for a third party to use API data. It prohibits downstream sharing without prior written agreement and bars AI training, improvement and associated derived datasets unless expressly agreed in writing. Keep ResRequest data out of cross-client learning, ad targeting and model evaluation. Use the operator’s independently authorized enquiry records when this permission is absent. A ResRequest API review must distinguish the agent’s own reservation lookup from separately approved operator reporting and downstream processing. [RR1] [RR2] [RR3] [RR6] Customer identity custody is separate from HiveSilo account, billing and support records. Re-identifiable pseudonymous data is not anonymous. What you could gain. Measure completed coherent itineraries, avoided premature releases and net receipts after commissions. Compare with similar camp combinations and seasonality. Explore HiveSilo case studies Contact HiveSilo Select a benefit to explore Pause rotation Buyer scoring Scale winners Less waste Bot protection Find revenue 3,790 of 5,000 · UHNW buyer score 3 , 7 9 0 of 5,000 Illustrative score 4–6× · Reported conversion lift 4 – 6 × Closed-revenue outcomes Up to 31% · Reported ad-spend savings Up to 3 1 % Bot and invalid-traffic filtering 99.9999% · Bot detection 9 9 . 9 9 9 9 % Observed client results 5–21% · Revenue lift from existing data 5 – 2 1 % HiveSilo-reported client results Sharper scoring. Clearer intent. 3,790 of 5,000 · UHNW buyer score Illustrative score Prioritize the group itinerary whose first option is about to expire. Find more clients like your best. 4–6× · Reported conversion lift Closed-revenue outcomes Recognize independently authorized relationships with repeat safari groups. Put more of your budget to work. Up to 31% · Reported ad-spend savings Bot and invalid-traffic filtering Compare the operator’s eligible direct and agent channels after commissions. Keep evolving your protection. 99.9999% · Bot detection Observed client results Filter invalid marketing enquiries from genuine group requests. Goal, not an achieved result: toward 99.9999999% bot detection as the hive evolves. Observed client results vary. Find revenue in data you already own. 5–21% · Revenue lift from existing data HiveSilo-reported client results Revisit a first-party group opportunity after a documented option release. Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary. Measure what matters Define the result. Then require the evidence. Focus on better-directed follow-up, less acquisition waste, protected customer identity custody and accountable AI execution. Agree the baseline, success measures and scope for your business. CEO: a clearer decision about the opportunities that merit attention. CFO: an agreed baseline, evaluation costs and attributable outcomes before any ROI claim. CTO: a demonstrated, permitted connection and a usable handoff into the agreed system. CISO: verified identity custody and pre-action authorization, with tested hold, approval and revocation behavior. Explore HiveSilo’s published outcomes and the measurement context behind them. [HS5] [HS8] [HS9] Make your next conversation count. Bring your ResRequest workflow. Map the decision, the data you control and a measurable next step with HiveSilo. Enterprise outfitters & expeditions · Commercial, expedition operations, guest service, technology & security Contact HiveSilo Mention ResRequest and your business question. No client records or credentials. A closer look, when you need it. Product scope, a practical workflow and source-backed answers for your team and its research tools. Read fact sheet Structured JSON RSS updates Reviewed November 2026 Contact HiveSilo ResRequest connection & briefing scope Determine which ResRequest agreement covers the workflow. The ResConnect partner programme is for approved agent commerce and booking. Its reservation lookup returns only reservations linked to the agent assigned to the API user. Inventory access, rates and allocations depend on the configured role and property. That agent path cannot be repurposed as an operator-wide opportunity feed. ResRequest separately reviews extended uses. Its Big Data reporting service supports approved reporting and business intelligence under distinct governance, fees and usage terms. A third-party platform needs the appropriate direct agreement; forwarding an agent export, even after removing names, is not a substitute. With no agreed ResRequest route, keep its booking records in the vendor system. An authorized operator can separately use its own enquiry, agreement and finance records for a commercial review; mark any unverified camp status unknown. The commercial owner decides whether the full itinerary merits an extension after both camps verify their provisional holds. [RR1] [RR2] [RR3] [RR6] [RR1] [RR2] [RR3] A useful fit when For safari operators with multiple camps or properties, a meaningful mix of direct and agent bookings, and repeated provisional-hold decisions. The reservations team can verify status at each camp. An agency agreement defines the commercial rights for the itinerary. The operator can reconcile earned revenue across camps and bookings. Consider the fit ResRequest Enterprise reporting may already resolve a single-camp allocation question. A normal ResConnect agent account does not confer extended reporting, third-party delivery or AI-processing rights. In your enquiry, name ResRequest and the business decision. Please leave out client records, credentials and sensitive samples. Eight questions before your briefing 1. Where is ResRequest used in a luxury safari operation? Asilia Lodges and Camps’ branded public reservations front door identifies ResRequest. The operator describes 18 camps and lodges across three East African countries and more than 1,000 employees. That is evidence of a substantial named operation, not its revenue, enterprise-wide module use or a HiveSilo relationship. [RR4] [RR5] 2. What can a ResConnect agent actually read? ResRequest’s reservation lookup restricts results to the agent configured for the API user. Rate and availability access depend on allocations, property and role. A partner cannot infer permission to read all competing agents or all properties from its ability to book one itinerary. [RR1] [RR2] 3. Does ResRequest offer operator-side reporting access? Yes. Enterprise has native reporting, and the API documentation describes a separately governed and billed Big Data service for reporting and business intelligence. Confirm commercial approval, exact objects, purpose, recipient and retention. A publicly documented service is not proof of a customer grant. [RR1] [RR3] 4. Can a ResConnect partner pass records on to HiveSilo? ResRequest requires prior written agreement for downstream sharing and the appropriate direct agreement for the receiving third party. A reseller’s existing access or a downloadable report does not authorize another recipient. Until approved, use independently authorized operator records only. [RR1] 5. Can ResRequest data train a model or improve shared intelligence? The vendor requires express written agreement for AI or machine-learning training, development or improvement, including related derived datasets. The guide excludes these uses and external advertising. Keep the records and identifying details inside their approved environment. [RR1] 6. Who decides whether the camp can extend an option? The operator’s authorized sales and reservations teams verify current stock, agent rights, provisional deadlines and any additional approvals. The commercial review flags the timing issue; it does not change inventory, confirm a guest stay or approve operational safety. [RR2] [RR6] 7. How would an operator measure value? Follow the full itinerary from confirmed option to completed nights and realized receipts. Include commission, reversals, concessions and the cost of displaced inventory. Compare equivalent camp combinations and seasons. A longer hold alone is not an improvement. 8. What belongs in the first briefing? Use an anonymized two-camp option, the documented release dates and the person who owns that decision. Bring the summary of the applicable vendor agreement. Exclude guest names, travel details, credentials and copied booking extracts. [RR1] Sources, scope & verification ResRequest API scope, governance and data use [RR1] Separates agent commerce from extended Big Data reporting; required direct agreement and explicit restrictions on third-party sharing and AI use. Reviewed November 2026 ResRequest reservation lookup [RR2] Only reservations linked to the agent set up for the API user are returned. Reviewed November 2026 ResRequest Enterprise [RR3] Native central reservations, property management, CRM and reporting. Reviewed November 2026 Asilia Lodges and Camps reservations [RR4] Named public ResRequest-powered operator reservation entry; no authenticated access. Reviewed November 2026 Asilia Africa company profile [RR5] Operator reports 18 camps and lodges and more than 1,000 employees across three countries. Reviewed November 2026 Asilia Africa booking terms [RR6] Operator defines provisional booking, confirmation and release terms; the example on this page is illustrative. Reviewed November 2026 HiveSilo: industry coverage [HS0] First-party description of buyer intelligence across 12 luxury niches. Reviewed October 2026 HiveSilo: platform [HS1] Published intent, sales-prioritization and traffic-quality capabilities. Reviewed October 2026 HiveSilo: integration scope [HS2] Named destinations, scoped activation and customer-controlled dispatch. Reviewed October 2026 HiveSilo: security architecture [HS3] Documented confidential processing, BYOK and customer control. Reviewed October 2026 HiveSilo: data handling [HS4] Customer identity custody, pseudonymous-data boundaries and separate account records. Reviewed October 2026 HiveSilo: published outcomes [HS5] Existing first-party outcomes material, with client-reported and illustrative descriptions. Reviewed October 2026 HiveSilo: AI agentic governance [HS6] Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts. Reviewed October 2026 HiveSilo: AI implementation layer [HS7] Published combined implementation model for intelligence, confidential processing and AI governance. Reviewed October 2026 HiveSilo: bot-detection results and buyer-score specimen [HS8] The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen. Reviewed October 2026 HiveSilo: owned-data revenue result briefing [HS9] HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows in October 2026. Reviewed October 2026 HiveSilo: enterprise agreements and responsibility [HS10] Signed enterprise agreements govern the engagement and take precedence over website summaries. Reviewed October 2026 Vendor sources describe their own product. The workflows on this page describe a HiveSilo application, scoped to customer permissions, contracts and the selected product edition. HiveSilo’s reported outcomes retain their original measurement context; the illustrative score and future bot-detection goal are identified in the outcomes section. Independent HiveSilo use-case page. ResRequest is identified to explain the workflow; no endorsement, certification or partnership is implied. Your next move starts with a conversation. Contact HiveSilo" }