Getting Started with N2CS

Learn how to set up and configure N2CS for your customer operations team. This guide covers initial setup, user permissions, and basic query operations.

Introduction

N2CS provides safe database access for customer support teams. It enables your team to access customer information without requiring developer escalation or risking system modifications.

With read-only access, approved searches defined by admins, and a full audit log, N2CS ensures safe and controlled data access. This guide will walk you through the initial setup process, configuring user permissions, and performing your first queries.

All operations in N2CS are read-only by design, ensuring your systems remain stable and secure.

Initial Setup

Before you begin, ensure you have the following:

• Read-only database access credentials for your customer data systems
• Administrative access to configure N2CS user permissions
• Network access to your operational systems (database, logs, CRM)

Step 1: Connect Your Data Sources

N2CS connects to your existing systems in read-only mode. You'll need to provide connection details for:

• Customer database (read-only user credentials)
• Log files or log aggregation systems
• CRM systems (if applicable)

All connections are established using read-only credentials. N2CS never requests or requires write access to your systems.

Step 2: Define Approved Searches

In N2CS, admins define and approve the searches that CS teams are allowed to use. This is a core principle of N2CS: CS agents can only select from admin-approved searches.

When configuring searches, you define:

• Search types: What types of searches are permitted (customer lookup, order history, account status, etc.)
• Parameters: What inputs each search accepts (customer ID, email, date ranges, etc.)
• Data scope: Which customer data sources each search can access

Once searches are approved, CS agents can use them, but they cannot create new searches or modify existing ones. This ensures controlled, safe access to customer data.

All user access is logged and auditable. Every query performed through N2CS is recorded with timestamp, user, and query details.

Basic Query Operations

N2CS uses approved searches instead of free-form database access. CS agents can only select from admin-approved searches, ensuring that every data access is intentional, controlled, and auditable.

This approach means CS teams don't see database schemas or have write access. They only see the approved search interfaces that admins have configured.

Customer Lookup

The most common operation in N2CS is looking up customer information. You can search by:

• Customer ID or account number
• Email address
• Phone number
• Username or login identifier

Each lookup returns structured information including account status, recent activity, order history, and support interactions. All data is presented in a clear, operational format designed for support teams.

Query Structure

N2CS queries follow a structured format:

Query Type: Customer Lookup
Identifier: customer@example.com
Returns: Account details, order history, support tickets

This structured approach ensures that queries are predictable, auditable, and safe. You cannot perform arbitrary database queries that might impact system performance.

Best Practices

Use Structured Queries

Always use the provided query types rather than attempting direct database access. This ensures your queries are optimized and safe.

Review Audit Logs

Regularly review access logs to understand how your team is using N2CS and identify any patterns or training needs.

Maintain Read-Only Access

Never request write access. If you need to modify data, use your existing systems and workflows outside of N2CS.

Keep Credentials Secure

Read-only credentials should still be treated as sensitive. Rotate credentials regularly and follow your organization's security policies.

Results and Integration

When searches are executed, results are delivered to Slack (if configured). Every action is recorded in the audit log, providing full traceability of all data access.

This integration ensures that CS teams can access customer data directly from their workflow tools without switching between different systems.

Next Steps

Now that you've completed the initial setup, you can:

• Review the N2CS Query Basics guide for more advanced query patterns
• Configure integrations with Slack to deliver search results directly to your team
• Review audit logs to understand how your team is using N2CS
• Train your CS team on using approved searches for common support scenarios
• Visit the N2CS homepage to see how CS teams use it