Scam With Your Friends Mouse and Keyboard Controls Setup

Getting your Scam With Your Friends mouse and keyboard setup right is the difference between a smooth shift and fumbling through a live scam call while the shift clock bleeds out. This guide covers default bindings, controller support, and how the input layer actually drives the call system.

Scam With Your Friends Game Overview and Input Demands

Before you touch a single binding, it helps to understand what the game actually asks of your hands. Scam With Your Friends is a first-person co-op job simulator from JakeHub and Metater, published by Jatater Worldwide, and it entered Early Access on 15 October 2026 for 64-bit Windows 10 and 11 at $9.99 with a 10% introductory discount. One to eight players run a scam call center crew inside a fictional Kolkata office, and the fantasy is exactly what the title promises: trick AI callers out of their savings, hit the daily quota, and survive a performance review from a rageaholic boss.

That premise matters for input design because your hands are doing three jobs at once. You are typing or speaking to a live AI caller, clicking through remote-access tools on a victim's computer, and dodging office chaos like computer viruses, police raids, and air strikes. According to the official Scam With Your Friends Steam page, the feature set includes real-time AI conversations, run-based progression, remote access to victim machines, an in-game paint app, a screen recorder, and a camera. Each of those tools wants a key or a click, which is why a clean layout pays off immediately.

Here is the practical breakdown of what your input devices are responsible for during a typical shift: the keyboard drives all locomotion and tool management — WASD or arrow keys walk the Kolkata office floor between desks, the interact key picks up headsets and answers incoming AI calls, and hotkeys toggle the camera, screen recorder, and panic tools when a police raid or air strike interrupts your scam. The mouse, by contrast, handles every precision task: aiming the camera to read a victim's screen, clicking through remote-access tools during an active scam, and drawing inside the in-game paint app. Because the core loop mixes constant movement with high-frequency clicks, your mouse ends up doing far more work per shift than the keyboard, which mostly fires in short bursts.

The takeaway is simple: the mouse carries most of your precision work, while the keyboard handles movement and tool switching. If you are still learning the broader loop, the beginner guide walks through the first-day flow before you worry about rebinding anything.

Default Mouse and Keyboard Bindings Explained

The stock layout follows standard first-person conventions, which is good news if you have played any co-op shooter or job sim in the last decade. Movement sits on WASD, the camera is bound to the mouse, and interaction lives on a single key so you can grab tools without hunting for a menu. Sprinting, crouching, and jumping round out the movement set, and the mouse wheel or number row handles quick tool swaps.

What surprises new players is how much of the scam itself runs through the mouse. Remote access to a victim's computer means clicking through their files, and the in-game paint app and screen recorder both rely on cursor precision rather than keyboard shortcuts. That is why mouse sensitivity is the single most impactful setting you can change on day one.

Experienced crews treat bindings as a shared loadout rather than a personal preference, because a mis-click during a remote access session can trip the victim's antivirus or close the file browser mid-transfer. The standard drift is toward left-hand movement, right-hand action: keep WASD untouched, move interact to a thumb button so you can grab a tool while strafing away from a suspicious cursor, and reserve the number row for tool swaps since the wheel overshoots under pressure. Crews that run the paint app and screen recorder back-to-back usually pair those two on adjacent keys, letting one finger toggle both while the other hand steers the mouse across the victim's desktop.

• Rebind interact to a side mouse button if you have one, so your left hand never leaves WASD mid-call.

• Keep tool-swap keys on the number row rather than the wheel, because the wheel is too easy to overshoot when you are panicking.

• Bind the screen recorder and camera to adjacent keys so you can toggle both without looking down.

• Leave voice activation on a push-to-talk key if your microphone picks up office chatter from teammates.

• Test every binding in the tutorial office before you join a public lobby, since a mid-shift rebind can cost you the quota.

One detail worth flagging: the 15 October 2026 hot fix notes mention that incorrect PC clocks were blocking AI access, and that speech startup crashes were fixed on some GTX 1650 and RTX 4060 Ti systems. If your inputs feel fine but the caller never responds, the problem is almost certainly the voice backend rather than your bindings.

Movement and Camera Sensitivity

Sensitivity is where most players quietly lose accuracy. A mouse that feels perfect for walking the office will feel twitchy when you are trying to click a specific file on a victim's desktop, because those two tasks demand different precision. Start around a mid-range sensitivity, then nudge it down by small increments until you can reliably hit a desktop icon on the first click.

The camera also matters more than it looks. You will constantly glance between your own monitor, a teammate's screen, and the caller's remote desktop, so a camera that snaps too fast makes those transitions disorienting. In practice, a slightly slower look speed paired with higher in-game brightness helps players track multiple screens during chaotic late-run shifts.

Tool Hotkeys and the Call System

The call system is the heart of the game, and it is where your keyboard layout earns its keep. Real-time AI conversations mean you are either typing responses or speaking them, and both paths compete with your movement keys for attention. Players who bind push-to-talk to a comfortable key and keep their typing hand near the home row report far fewer dropped calls than those who improvise.

The gameplay guide breaks down how the scam scenarios escalate across a run, but the input side is straightforward: the faster you can switch between talking, clicking, and moving, the more calls you close per shift.

Scam With Your Friends Controller Support Status

This is the question that splits the community, so let us be direct about what is and is not confirmed. As of the Early Access launch on 15 October 2026, the official store page and patch notes describe keyboard, mouse, and voice as the primary input methods. There is no dedicated gamepad configuration screen listed among the launch features, and the remote-access and paint-app tools are clearly designed around a cursor.

That does not mean a controller is useless. Steam's built-in controller configuration layer can map gamepad buttons to keyboard and mouse inputs, which lets you walk and interact with a thumbstick while still using the mouse for precision clicking. It is a hybrid approach rather than true native support, and it works best for players who want to lean back during the conversational parts of a shift.

Here is how the two input styles compare in practice: mouse and keyboard wins on every precision task — remote-access clicking, typing call responses, and the paint app recorder all demand a cursor that a thumbstick simply cannot match — while a mapped controller only closes the gap on walking the office and voice call responses, where no fine aiming is required. That split explains the hybrid setup many crews settle on: gamepad in hand for the conversational stretches of a shift, mouse within reach the moment a remote-access job or recorder task appears.

The honest verdict is that mouse and keyboard remains the intended way to play, and a controller is a comfort accessory rather than a replacement. If you want a deeper look at how the run structure rewards fast input, the beginner mistakes guide covers the habits that cost new crews their first quota.

Setting Up a Hybrid Gamepad Layout

If you want to try the hybrid route, the setup is less intimidating than it sounds. Open Steam's controller settings for the game, choose a template, and map the left stick to WASD, the face buttons to interact and jump, and leave the mouse untouched on your desk. This gives you analog movement with full cursor control, which is genuinely pleasant during the slower conversational stretches of a shift.

The tradeoff is real, though. Every button you map to a keyboard action is a button you cannot use for something else, and the game's tool set is wide enough that you will run out of comfortable inputs fast. Test the layout in a solo lobby before bringing it into a full eight-player crew, because a mis-mapped panic button during a police raid is a memorable way to lose a run.

Why Voice Input Changes the Equation

Voice is the wildcard in every input discussion. Because the AI callers respond to real-time conversation, players with a working microphone can skip typing entirely and keep both hands on movement and clicking. That effectively turns voice into a third input channel, and it is the reason many crews designate one player as the talker while others handle the technical tools.

The 15 October hot fix moved Qwen3 voice downloads to a dedicated server and now warns players before hosting or joining when the higher-quality voices are not ready. If voice input feels laggy or unavailable, check that warning before you blame your headset.

Optimizing Your Setup for Long Shifts

A scam call center run can stretch long enough that comfort becomes a performance stat. The office is deliberately chaotic, with viruses, raids, and air strikes interrupting your flow, so a setup that keeps your hands relaxed through hour three will outperform a theoretically optimal layout that wears you out by hour one.

Practical adjustments that pay off across a full session: bind push-to-talk to Left Ctrl rather than a thumb button so your pinky anchors it during long remote-access stretches, and lower your mouse DPI to around 800 while raising in-game sensitivity to compensate — this combo keeps cursor placement precise when you are clicking through a caller's desktop while a raid is closing in. A wider mousepad also prevents camera sweeps from running off the edge mid-scam, and disabling OS mouse acceleration ensures your flick to the disconnect button lands where muscle memory expects, even after three hours of virus pop-ups.

• Lower your mouse DPI slightly and raise in-game sensitivity instead, which gives you finer control over remote-access clicking.

• Use a large mousepad so wide camera sweeps never run off the edge mid-call.

• Keep push-to-talk on a key your left pinky can hold without straining, since you will hold it constantly.

• Disable mouse acceleration in your OS settings so your cursor lands where your muscle memory expects.

• Test your microphone gain before joining a lobby, because a hot mic that clips will make AI callers harder to understand.

• Sit at a distance where you can read the caller's desktop without leaning forward, since remote-access work is detail-heavy.

If you are running the game on a lower-end GPU, the hot fix notes about GTX 1650 and RTX 4060 Ti speech crashes are worth reading before you assume your inputs are broken. A stable frame rate also keeps your mouse feel consistent, which matters more than raw sensitivity numbers.

Sensitivity and DPI Starting Points

There is no universal magic number, but a sensible starting range helps you find your own. Most players land somewhere between 800 and 1600 DPI with in-game sensitivity in the middle of the slider, then adjust in small steps over a few shifts. The goal is a setup where a full mousepad sweep turns you roughly 180 degrees, which is enough to check a teammate's screen without spinning past it.

Once you find a value that works, stop tweaking it. Constant sensitivity changes destroy the muscle memory that makes remote-access clicking feel automatic, and that automatic feel is exactly what keeps your quota safe during a chaotic late-run scramble.

Common Input Problems and Fixes

Most input complaints in the first week trace back to a handful of fixable causes rather than genuine hardware faults. The launch window brought a wave of reports about calls not connecting, tools not responding, and multiplayer hiccups, and the developers shipped hot fixes for several of them within the first day.

The pattern here is that the game's input layer is stable, but its voice and networking layers needed early patching. If your mouse and keyboard behave correctly in the tutorial but fail in a live lobby, the issue is almost always backend rather than binding-related.

When to Rebind Versus When to Adapt

Not every awkward key deserves a rebind. Give a new layout at least two full shifts before you change it again, because early discomfort is usually unfamiliarity rather than a genuine mismatch. Rebind only when a key physically blocks another action you need at the same moment, such as holding push-to-talk while sprinting.

Players who chase the perfect layout every session end up with no muscle memory at all, which is worse than a slightly imperfect setup they know by heart. Pick a layout, run it for a week, and only then decide whether one specific key needs to move.

Reporting Persistent Input Bugs

If a binding genuinely does not register no matter what you try, the official community hub is the right place to check whether others hit the same wall. The official Scam With Your Friends Discord grew to roughly 49,000 to 50,000 members within a day of launch and is the channel the studio names for bug reports and support tickets, so a quick search there often reveals whether a fix is already incoming.

Frequently Asked Questions

Does Scam With Your Friends have native controller support?

As of the 15 October 2026 Early Access launch, the official store page and patch notes list keyboard, mouse, and voice as the primary inputs, with no dedicated gamepad configuration screen. Steam's controller mapping layer can emulate keyboard and mouse inputs, but that is a workaround rather than true native support.

What is the most important binding to change first?

Mouse sensitivity matters more than any single key. Because remote access, the paint app, and the screen recorder all depend on cursor precision, dialing in a sensitivity where you can hit a desktop icon on the first click improves your shift more than rebinding interact ever will.

Can I play entirely with voice instead of typing?

Yes, if your microphone works reliably. Real-time AI conversations accept spoken responses, which frees both hands for movement and clicking. Many crews assign one player as the dedicated talker while others handle the technical tools, which keeps the call flowing without typing delays.

Why do my inputs stop working mid-shift?

The most common cause is losing window focus after alt-tabbing, which makes the game ignore clicks until you refocus it. If inputs fail only in multiplayer, check the hot fix notes about Steam network congestion and the PC clock issue that blocked AI access at launch.

Is a controller better for long sessions?

A controller is more comfortable for the conversational stretches, but it struggles with remote-access clicking and typing. A hybrid setup using Steam mapping for movement while keeping the mouse for precision work is the practical middle ground, though mouse and keyboard remains the intended way to play.

Final Thoughts on Input Setup

Your Scam With Your Friends mouse and keyboard layout is not a cosmetic preference, it is the interface between you and every scam you pull off. Nail down a sensitivity you trust, keep interact and push-to-talk within easy reach, and treat controller support as a comfort option rather than a replacement for the cursor-driven tools. Do that, and the chaotic office around you becomes noise you can ignore while you close calls and hit quota.